Well for one it provides multiple MIDI ports, so while you're in a regular host you have the 1-16 channels and you're done, in a VST3 (or the tortuous workaround in a version of the plugin created for Logic "Event Input" {supposed to be addressed since the AU3 protocol came out}) VE Pro instance we enjoy up to 48 Ports. In case you aren't following, this is 48 x 16 channels. I only tell it I want 16 ports. It's useful.
I use it for 98-99% of plugins, for numerous meaningful reasons: first of all it is a separate process than the DAW, so it's 1) more stable; 2) a better use of resources in terms of multicore distro; 3) the save and load times are not tied to the DAW so it saves time (also ties in with stability) as a preserved and decoupled frame.
THEN, all the plugins automation is in a single map so setting up automation at the DAW end is simplified. 4 instances is 4 instrument channels with parameters, vs dozens, and then there's FX channels. All in one map for the instance.
So, it opened mixing up for me, detailed extensive automation being key.
The 'non'-pro version only hosted VSL libraries and then some Apple stuff which came with the AU development package, I don't know how it evolved, I embraced Pro around a decade ago.
Maybe better to stick to discussing things you know about.