I also do understand your original question, because the DAY before VEPro released (and I was waiting patiently!) I had just finished setting up a large template that replaced 7 gigastudios on seperate PCs, with just ONE mac using bidule and VE2, and Kontakt. I was waiting for VEPro of course, but had to get going as setting it up took at least a week of careful setup and I had a deadline for a film project to start with this.
I ended up with a large bidule setup, with Kontakt instances and VE2, East West Play etc inside bidule, under ReWire for use with DP6, all on one Mac.
I got it working great, though I had to extend from using only bidule under rewire, to also using 3 instances standalone of VE2 to get everything I needed, and these were handled audio wise via physical audio adat loop back (2408, Banks B and C which I previously wasn't using). I also had to add a standalone instance of Kontakt (which thankfully has 4 midi pots (16 channelsx4) to handle everything.
One neat thing about all this is that when I open and close cues in DP6 (and I use a seperate project for every cue, it has to be this way for reasons I won't go into), the template remains the same, no reloading of anything and no disconnect or connect buttons, nor is there any need for "preserve" features. The standalone VE2s and Kontakts sit in the background and work without any of that needed.
Then VEPro came out the very next day. In my case I experimented (remember I'm only using one Mac) and found that VEPro has only one port per instance in DP (AU) so I'd have to load a number of them in DP as a plugin if I went this way, and be sure to keep an eye on "preserve" features when switching between cues / projects in DP. I'm actually tempted at this point to keep my "old" set up because there's no need to worry about that, although VEPro instances (as a plug in) would offer me more audio channel options.
A long way of saying I see where you are coming from, as when you end up with about 60 cues for a film and you open and close them a lot on certain days, it's just an extra thing to keep an eye on that I was wondering about avoiding. I've since heard the VST and RTAS versions of VEPro don't have this limitation, so you wouldn't need as many plug in instances in that case, but my DP system is AU.
(Note this entire experiment is very specific to the use of one machine for both sequencer and VEPro. When it comes to wanting to use an extra computer, that's where VEPro truly blows everything out of the water and demonstrates just how completely revolutionary it is. I'm not forgetting that!)