All well and good but I don't deal in templates as I find modifying a template takes up more time than working from scratch. I never know until I actually get started on a piece of music how I'm going to orchestrate something - it might be synths, orchestral libraries or a mixture of both. Sometimes I'll start in one way and end up with something completely different. Also you're talking about loading while the main thing I'm trying to find out about is saving. I already have my server computer set to automatically load a VEPro 64 instance on startup.I recommend saving your VE Pro templates as well as your DAW templates decoupled. While in theory, having them coupled so that VE Pro automatically gets populated for you by opening the DAW template sounds great, in practice, the DAW project has to constantly remember "look over there, find that, load that" and becomes bloated and more prone to corruption.
Instead I suggest you:
1. Open VE Pro and load your template.
2. Open your DAW and load a decoupled but "connected" template so that they automatically connect.
Again all I want is a simple explicit set of steps of what to do when saving a daw session - what to do inside VEPro (if necessary) and what to do in my daw. Shouldn't be that difficult to write up. I'm surprised something like this isn't in the manual given all the other good info in there.