+1 for track templates, since they can be surgically inserted into projects. A "be all, end all" project template, especially loaded with VSTis will bring a CPU to its knees fairly quickly, but track templates can be inserted as needed. A track template can also be a folder (everything for the track template in that folder, then save a track inside it as a template). That is not as intuitive to save, but is more useful with VSTis with multiple ins and outs. Once you get a feel for how they are saved, and what they recall (associated busses, bins, etc.) you will begin to see how useful they are.
A simple way to get them is to open any cwp with good routing and save track templates from them. Your own project would be easiest, since you know them, but any cwp works (like demos from the past).