Yes it would be nice to get less ignoring, but if you can do that also depends on how many customer requests you get vs the size of team you can afford to have.
And some of the biggest companies in the world with billions in profit also have set a bad precedent in that regard.
Well the voting system is something that could help. Other big companies have idea boards where users can vote for features and changes. And these are considered and implemented.
On this board this feature is not advertised, ppl has limited votes, and often they confuse 
a message vs voting a post.
Between me and myself I dunno how much the votes are relevant in order to prioritize a feature or fix a bug. So yeah there is still a long way to go.
In defence of Steinberg the survey we received seems a good call to address user feedback, but as for everything, I will judge when I see actual results.
I’m getting this issue from time to time. Today it’s NI Bite, where bypass automation sometimes works and sometimes does not. Insert on an audio track.
It’s random and rare and I don’t even remember with which plugin I had this issue before. It’s possible that it was Replika because I’m using it a lot.
It isn’t easy to reproduce it because it has only about a 25% reproduction rate (in playback) in one project out of probably 50. So I can only wish good luck to devs to catch this bug 
It never happened in C13 or earlier versions.
Mac Mini M2, Sequoia
I sent them a demo project with just 2 tracks and stocks plugin + Replika, and a video of me reproducing the issues it should be straightforward if they get the issues as i do.
The issue happens by the way when you reopen the project.
You set the bypass, do your stuff all is good, then you save, close and reopen and is broken.
One thing that changed from Cubase 13 to Cubase 14 on Windows, is that Cubase 13 defaulted to allowing VST2 plugins, and Cubase 14 defaults to exclude VST2 plugins.
So my theory currently is:
It’s possible that the different behaviour is caused by the same Cubase project using the VST2 plugin in C13 and using the VST3 plugin in C14. – This may not be obvious unless you specifically look for it.
So if the Bypass handling has to be programmed slightly different in VST2 vs VST3, it’s possible that some plugins have a bug in their VST3 versions, that wasn’t in VST2.
From a variety of impressions with different plugins, I’ve come to suspect that something about Bypass handling has changed from VST2 to VST3 and not all plugin makers have gotten this right in all of their plugins.
p.s. Just now, I was also able to find a thread that seems to imply exactly that:
It’s a very interesting discussion and seems totally related, thanks for sharing.
OK so ParameterInfo is a type descriptor for parameters, that has all their properties, the title, the units, the default value etc. Then it can be “decorated” with these flags, such as if it’s hidden, if it can be automated and if it’s a parameter of type bypass. This last one is automagically connected to the general bypass system. But this thing is new since VST3 because earlier was using something else (callbacks?)