By expectation, do you mean you wouldn’t want other developers’ plugins to get a badge which says “VCV Visually Impaired Accessibility Collection 
”?
As a hobbyist developer, I don’t understand how VCV leaning into highlighting more accessible modules would place any kind of financial burden on hobbyist developers. In this case it seems like the only people who would really care that you don’t have a would be those who you weren’t ever planning on catering to anyways.
I don’t think that breaks the dark mode paradigm. Each of your panels would need to be labeled dark, light, or both. Users would set their default light panel and default dark panel separately. When Rack would signal to switch from light to dark mode, each module would switch from the default light panel to the default dark one.
The decision was made 9 months ago, but as you can see on GitHub there was no further discussion until 2 days ago. Some of this thread ought to be taking place over there instead. It wasn’t until now that we’ve had someone publicly announce they are prepared to provide people with a way around the lack of an official option, so I think it makes sense to cover all the angles here.
The whole uncomfortable discussion about licenses on the graphics, and how much of the design is covered by CC vs how much is covered by GPL, and perhaps how much of it may be in the realm of patent or in fact represent totally un-protectable elements of the design and therefore actually not covered by either license at all… It can all be avoided if it turns out that the original decision was made on a false premise and may be reversed.