Suggestion: Command SayVar for accessing configuration settings

Currently the individual option settings in the Tag Source, the configuration values, can only be accessed by the logical functions:
IfVar "key" "value"
IfNotVar "key" "value"
where the key is used to access the setting which is compared to the given value.
This only works efficiently for values of type bool (logical) and for type strings with given choices to select from. There is no method available to read the other possible value types number and string (with arbitrary text input) in a websource script. A solution for a special, restricted case has been described by @rboss in An efficient method for assigning numeric inputs into %output%.
In my example I want to use a configuration value of type text, that allows me to enter a name that the script later can use as a name of a tag:

{
	"type": "string",
	"key": "Tag_Notes_Setting",
	"title": "Tag field for notes",
	"description": "Tag field to use for notes.",
	"choices": ["none","COMMENT","NOTES","UNSYNCEDLYRICS"],
	"default": "COMMENT"
},

For the user to provide a name not in my list of choices I had to use the above code without the choices, but then I see now way to read the value the user did enter.
Therefore I want to suggest the command:

SayVar "key"

that reads the (read only) configuration values and copies the value into an output buffer designated by the most recent outputto "NAME". This should work for any type and make it possible to really efficiently use all possible configuration options.

Another benefit would be if this was available:

Only further amendment would be output buffers created by settings might need prefixed automatically by Mp3Tag with “Var_” to distinguish from any other created outputs.

Just noticed some very similar and additional/alternative ideas from this thread:
Suggestion: 'Splice' command for WS - Development / Web Sources Discussion - Mp3tag Community with $var(name) as an option. @AreDigg

Thanks for the suggestion -- and all the others who have suggested this before! I've implemented this with this internal test version and hope it works as expected:

https://download.mp3tag.de/support/F3F01D59-10F6-4D80-913A-7E8E38EA8B58-3-31-11-3/mp3tagv331k3-x64-setup.exe


For the other suggestions, I'd really love to see separate topics for each idea so they don't get lost after this one is marked as solved and can be tracked independently.

So many new things coming to the framework, I have to take a look at it all.

Wow, that was a fast response to the wish for this new command. It works properly, and I want to thank you @Florian ! Sorry for not taking time to search for and mention all the others how had proposed this or a similar feature before.

Thank you! This is now also supported officially in Mp3tag v3.32.