This is exactly the problem. Steinberg doesn't listen to plugin vendors (or if they do, the response is very slow to come, it took how many years to reintroduce the legacy methods for CCs and stuff to VST3?) and just do things their own way, and it's their way or the highway...
The problem that dewdman42 explains is real, you've got the usecases explained where it is real and current VST3 "way to deal with that" is flawed because not all DAWs support VST3 fully, so there is no real solution that would behave identically across all DAWs. That is the crux of the issue, and this is why Steinberg should have had sat down with a bunch of plugin and host developers BEFORE VST3 was released to sort all this shit out. The problem is real, but the worse problem is Steinberg doesn't want to admit there are problems.