Edit: sorry, I just noticed that there was a template I could've used for formatting this. I somehow initially didn't notice on my phone and deleted it.

The ability to change custom Options outside of the /wa menu would be beneficial and pretty powerful in some cases.
Maybe a dedicated switch to enable this on a per-option basis instead of applying this capability to everything.

Motivation

There's many possible applications of this, but here's the one that made me write this request:

Recently on the WA Discord, someone asked for help with creating a radial CD tracker timeline. Someone linked pre-existing similar alternatives, and I noticed how all of them require multiple packs of auras to handle multiple specs.
Meanwhile the WoW API offers you to retrieve a specs entire spellbook at will. While this would probably allow you to simpify all of those packs into a single TSU that automatically creates all the auras you need for any spec you play, it also means that you'd have populate your custom options tab manually with every single CD spell for every spec if you'd want to give the user customisation options, and you'd also have the annoying task to keep that big list up2date every patch. (You could also just let them customize based on spellIDs or names they enter themselves in some boxes, but that's user unfriendly/hard for many regular players)
If you could dynamically add things to the custom options from code, then you could instead just generate option keys automatically for only the spells you need. It'd be automatically up2date, and very user friendly I'd say.

This is just a random example, there are probably infinite more where it'd be beneficial to be able to do this to create more universal and easier to maintain WAs in some cases.

Possible Issues/Considerations

Obviously these use cases could just be fixed by making a dedicated add-on for them. But then again every single use case of WA could also be solved instead by making a standalone addon, but WA is so powerful and user-friendly that it's superior to just use it for these. And adding this feature would offer even more powerful and universal applications I guess.

I'm aware that this would probably clash with the fact that WA runs the on-init code block on options change, but there should be a way to circumvent that for specific option keys if you wanted to I'd hope.
I know this kinda goes against the current intended use of the custom options tab, but that doesn't mean it can't evolve over time I'd hope.

Or are there other technical limitation that I'm obviously completely unaware of (as I'm not really clued into the inner workings of WA) that make this entire thing impossible?

Best wishes and thanks for reading,
dntsy

That goes far beyond what custom options are supposed to do.

I'm aware, as I wrote:

I know this kinda goes against the current intended use of the custom options tab, but that doesn't mean it can't evolve over time I'd hope.

It may go beyond its intended scope now, but is there really no way this can change in the future?
I see this as a pretty powerful feature in some cases, what would be the downside of it that prevents it from ever being considered?

Outside of the work needed to make it happen obviously.
I'm just curious what motivates the thought process behind outright rejecting to even entertain the thought.

That goes far beyond what custom options are supposed to do.