I wasn't sure what would be involved, and if it's too much that's fine... just thought I'd suggest it as I'm wading through WAY too many automation channels at the moment. Some of which are definitely my own fault.
The idea tho is it's not meant to be used as something that gets changed in identchannel... you set it once when you create a widget and that's it. Once it's marked non-automate-able, it's stuck that way for the instance. And changing what elements are available to automate makes it appear almost like an entire new plugin to a daw... so that is definitely not my intended use. I think of it more as a way of "hiding" elements that you may want visible and/or interact-able but not automate-able.
I can't remember why I was having better luck with a checkbox in some cases. I think maybe because I was originally setting it with simple 0|1 values to the main channel as a shortcut rather than having to format an identchannel statement, or maybe because I was flipping it too quickly as a clip light? I can definitely skim some stuff down to images (I've already been doing some of that) but I don't know, I feel like even ignoring those examples this would still be pretty useful.
For a better example (or maybe not, I dunno)... disabling automation on buttons that affect/interact only with the instrument's gui, for instance making a window popup or close, or changing which element of a few similar ones is visible.