Your "TechnicalUser" identity threw me off. If you could do this in VB, a rudimentary add-in won't be too hard for you. You can hook the add-in up to a toolbar button and/or an AutoKeys macro.
First, study the Modules and Module objects to learn how to edit modules in code.
Then, create a separate database for your add-in and write code that prompts you for a control name or whatever, builds a procedure as a single string with embedded CrLf's, and puts it in a multiline text box on a form. That will give you a means of debugging the add-in. You can't actually write to a module while you're debugging, because editing a module in code interrupts the debugging interface, making it stop working for a while.
When you've got it working smoothly, you'll need to make changes so that it actually updates the currently open module in the database being developed, and create a USysRegInfo table so it can be loaded as an add-in. I need to leave for work right now, but I'll give more details later if you want to pursue this.
BTW, do you know how to write text parsing code? If you do, you could make your add-in fancier and more flexible. Rick Sprague