You are correct. In this instance, some would argue that the current "tag" doesn't go far enough. So they would replace the functionality of the tag instead of providing additional tags for further povision. The problem here is that the documentation is slim enough that you might miss some endearing features if you do indeed rewrite such a function. So, my solution is to just add another tag to provide the functionality that I need, and keep my own docs on my own tags. That way, encapsulation is more reliable as I'm not trying to jam a feature set into a single tag. Yes, the tag count grows, but it's documented well. Documentation has always been a problem for languages. It's one of the reasons I'm migrating languages now. Development resources are a major part of finding out how to get around obstacles.
There is no iterate or routine for this type of programming. It's more FileMaker style. I was thinking range, and that's what I searched for, and nothing came up. I think in terms of iteration than qualifying a test cell. That to me feels like a workaround that we had to do in FileMaker for so long. It feels super dirty.