All well understood - and the wish to have them is definitely clear!
Most of these could actually be addressed by providing a Re-Wire (or similar) interface to Cantabile, without fully wrapping Cantabile in a vst3 container. This would be lots easier to implement, without all the changes that would be necessary to make Cantabile work well as a plugin.
In fact, there is a lot of your list that can be done today (not the offline rendering part - agreed), if you use virtual audio and midi cables to wire Cantabile to your DAW - I’ve done this a couple of times. It’s a bit fiddly, but works.
But the key point: Cantabile is built with one top priority: to play VST instruments live - and in this area, Cantabile excels! Anything that pulls @brad’s valuable intellect and capacity away from this top priority - and anything that compromises Cantabile’s capabilities in this area - would be very difficult to accept for Cantabile’s core user base.
I can understand that Cantabile’s capabilities will be attractive for all kinds of other uses, but to me it is important that Cantabile is first and foremost a tool to use VST instruments and effects in a live setting - and it will continuously be optimized to excel in this task!
And if by adding too many features outside its core purpose, Cantabile becomes too complex or its performance suffers, this would definitely damage the core product - don’t take feature bloat too lightly. I really appreciate @brad’s way of weighing feature requests against the big picture continuously - I hope things stay this way!
I’ll always vote for live use as the top priority, any other features and feature requests need to be carefully evaluated in their potential to support or damage that priority.
There are tons of various tools for producers and film composers, but there are very few applications that can do what Cantabile does for live musicians - this is its core market, and I hope it stays that way. Cantabile has changed the way I work live, and I wouldn’t want to go back!