Hey that sounds pretty much like the issue we reported here a few days ago:
We talked to the Cubase Developers a bit and there was the assumption that the reason for this issue only occurring with Cubase 11 could be related to the combination of the macOS SDKs both the plugin and Cubase have been built against. We are still seeing this issue on only a limited set of our own macs and didn’t succeed to build a reproducible test plugin that confirms this assumption
