Under the new framework, this seems like COMBINATOR. Although right now, combinators don't let you choose the name for INPUT, they're all stylized to assume INPUT is the name.
We'll definitely have something like this, that you can use for making a rule that you reuse...or just for calling directly.
GET-GROUP! is looking like it's going to stay on track as a way of saying "evaluate this group and then splice the result into the parse stream". Since LOGIC! true means keep parsing (as does VOID), and LOGIC! false means stop parsing, this is useful for many cases.
You could always capture, and say:
[x: capturing rule, :(test x)]
And that gives you one way of doing things. If the rule fails you'll be rolled back to where you were before the capture. Though it's not letting you scan and move the output position arbitrarily.
Okay, thanks for reminding me what APROPOS was. Not particularly related to parsing, but it does relate to binding.
Ren-C continues to strive to be a substrate for exploring binding ideas...I did this little writeup to try and look at it from the big picture:
Binding Re-Examined From First Principles
The technical parts are trying to get better while staying functional. I'm not that worried about slowing things down if I can get at some answer that is right for some definition of right that lets you do cool things. I just feel historical Red and Rebol has only let you do broken things...