I repackaged some software recently to compile as plugins (used to be standalone).
One of the programs was, among other things, a JUCE based VST/AU host. I assumed I would have to change the config and drop out that portion of the code to get it to run properly, but left it in at first, thinking JUCE would probably be smart enough to change config flags as needed.
To my great surprise, not only did it compile perfectly straight away, but it even maintained the hosting capability. The plugin read an xml config and successfully loaded several other plugins immediately. I checked the sound, and everything seemed fine.
I am amazed that a plugin can also function as a host, but wonder if there aren’t some serious issues here I am not seeing here.
Other than the expected latency concerns - there must be some other reason not to let a plugin be a host?