While this specific bug may not have been called out, the fact that parameters have never worked 100% properly through the various iterations of AudioProcessorParameter/AudioProcessorParameterWithID/AudioProcessorValueTreeState HAS been mentioned. Many times. For example:
Please stop reinventing parameters in the pursuit of “improving the interface” and put in the time and effort to (a) truly understand the nuances of parameter implementations for the various plug-in formats and (b) chase down the corner cases that make the difference between a 90% solution (“Look, the demo with two sliders works in one host!”) and a 100% solution (works in every major host, displays correctly for “generic” UIs, works properly with automation in all modes, works properly with control surfaces, all types of controls work properly (toggle/stepped/continuous, integer/float/named), handles forward/backward compatibility gracefully - including addition, deletion, or reordering of parameters). Yes, these things are hard and time consuming… which is why those of us who invested time in developing custom classes to do all of that are resistant to breaking changes forced on us without a similarly comprehensive solution.