I'd like to see some numbers about the first claim, seems dubious. Have you done any comparisons? I somehow doubt VSL forum is a good source for that kind of info. (Its like asking on Logic forums whether logic is great)
As far as second workflow goes, could you describe it a little more? I dont think i understand correctly. What does this achieve compared to using logics templates, whats different?
Ploki, regarding the core distribution...I have actually monitored this, and it distributes the loads across all cores as opposed to single core only. Based on my experience, sessions in Logic are much more smooth when hosting in VEPro. However, if I'm just using a modest track count, I don't usually bother. BTW- the VSL forum is a great resource, it's very informative and its members are users of pretty much all major DAW's. Plus, their support is very good, and a free trial is available upon request.
Using a VEPro template is not like a Logic template. In a Logic template, everything needs to reload when you close and open/create a new project. With a VEPro template, you just load once....it all remains preserved until you close it. So if you were to close and start (or open) another project, all the VI's are already loaded. This is a HUGE timesaver when dealing with large templates and working with multiple projects (for example, 75 cues for a film). In a regular Logic template, you would need to sit there and wait for everything to load up every single time.
I just wrapped up a big project, consisting of twelve tracks, each with three variations. My template (for the whole project) consisted of 98 tracks (Kontakt, Play, Omnisphere, etc), so imagine how much time would be wasted every time each cue was opened up (especially with an editor reminding you of a looming deadline ). With VEPro, it just a matter of seconds. But if you are only working with a handful of tracks at any given time, you may not find any benefit. All depends on your workflow.