Variable / array local or global dependent on special character in its name and tasker config setting

When creating a task, it's likely to have a certain number of global variables / arrays global to be able to check their content for debuggung.

When having task development finished, certain global variables / arrays should be local because they are much more run-time efficient than being global.

It's a certain work to change global variables / arrays to local and also a certain risk to miss a variable / array somewhere in an action, and task doesn't work no longer as expected.

My proposal: Would it be possibe that variables / arrays with an e.g. leading or trailing special character are handled as local or global, dependent on a tasker config setting? Then, during task development, when config setting is "global"  all those variables / arrays with that special character would be handled as global, and their values could be checked during task debugging. When task development is finished, config setting could be set to "local" and all variables / arrays with that special character would become local and run-time efficient.