I don't really see the point of VEPro to be honest. My orchestral template is massive, and working directly inside of Cubase has proven to be the most hassle-free. All of my template tracks have a cc1/cc11 reset message at the beginning of them, and each are frozen. So I can load a template with 200+ tracks instantly. If I need a track, I just unfreeze it, which takes 2 seconds. VEPro supposedly makes large templates easier because you can decouple the sample save/recall from your host, but you still have to load that massive amount of samples at some point. But, a Cubase template with frozen tracks means you will only load the samples you need when you actually need them. Zero waiting time for anything.
I own VEPro, and the biggest problem with it is the bussing. I use Instrument Tracks - I do this because I constantly need to EQ, effect, and tweak the audio associated with each track. It's easy to assign a hotkey to open the Channel Settings window for the selected track. I want the EQ for 1st Violin, I select that track and press my Channel Settings hotkey. When using VEPro however, the general workflow is to create a server and connect to it via multiple MIDI tracks -- so if you need to find the audio output associated with a given MIDI track in a large template...good luck to you. And when you select that audio track, guess what happens - your MIDI track is unselected, so you can't play a note on your keyboard and hear the change you made to the audio output...you have to go back and find that MIDI track again. Infuriating. Separate MIDI and audio tracks is so 1997.
The other problem is automation. Automation parameters for plugins hosted in Cubase show up by name. I have track Quick Control assignments tied to each instrument in my template, and they can be intuitively automated. When using VEPro however, you get destination names like Parameter 1, Parameter 2, etc. Seriously, what the heck is that. Who knows what "Parameter 1" is controlling. I sure don't.
VEPro is like most other hosts-within-a-host -- it inserts this additional layer between you, your plugins, and your workflow. Everything you do is one extra step, even if it supposedly does better with x64 core handling blah blah blah. I sure didn't notice any improvement. It's one of those products I just don't get. I think it's mostly useful for people who need to wrap VSTs somehow (ProTools or x86 Win users).
Lol, sorry to be so negative - your mileage may vary ;)