Regarding the overload indicator, I agree. It’s a known issue for years, and I have grown to ignore it. But I don’t know if it’s technically a bug. Too many process functions occur in the project loading process. What would help is a KC to reset the indicator once the project is loaded. Sometimes I manually reset it to enhance good vibes, but within minutes it’s lit again. For myself it has no use unless it happens with a audio drop-out, but then again, who needs a indicator for that?
Making the assumption that a plug continues to crash after 6 months of C11 being released is IMO a bad assumption. Have you contacted Cherry Audio to check their data base for any Cubase issues? Have you found forum posts of users of Cherry Audio with the same issues? If similar experiences aren’t found, what do you think this could possibly suggest even though it works in other DAWs?
Another idea is to temporarily save C11 preferences on your desktop. Then make sure any prior Cubase versions you have a license for, are re-named or hidden. It’s very important to isolate C11 only so it can’t suck prior Cubase data. Then trash preferences, and start Cubase which will re-build. Add the Cherry Audio plug. Do you get the same issues then?
Suggesting this isn’t your obligation or that we are all beta testers may indeed be true, but it won’t get your issue resolved.
Do you have earlier Cubase versions that worked as intended? If so, prior to purchasing C11, did you run the C11 demo with Cherry Audio?
I don’t consider myself a hero, but I’m pretty sure VST is simply a framework, and as you probably know, a lot can happen inside VST that is beyond the VST creators design regardless of VST2/3. I’m even guessing you know “Professional Audio Software” is a marketing tool?
Have you considered using what works better for you? Personally, I would place dozens of issues in front of the load indicator. And no one, except possibly Steinbergs code teams understands the financial cost of that fix. It may not be a simple fix. Maybe they should simply remove it from prior versions? Fixes are always about limited financial resources, and obtaining the best value for the greatest number of users.