I noticed that if I save a track as a template when it happens to be in a folder, and I insert that track template into a new project, that folder will be inserted into the track template.
Where this becomes a problem is when I need to insert the same template multiple times, I get multiple copies of that folder.  For example if I have a Lead Guitar track template and I insert it into a project, I get a track named Lead Guitar in a folder called Guitar.  But if I load that template in a second time, I get a second track named Lead Guitar in  a second folder called Guitar.
Or I might have a project template which has a folder called Synths.  I also have track templates for various synths, which will show up in a folder called Synths.  Wouldn't it make sense to have these tracks be inserted into the existing Synths folder instead of creating multiple Synths folders?

I think you need to create a track template for each situation.
"Guitar 1 Track" "Guitar 2 tracks" and so on.

Maybe put forth a feature request to ask them to add a check box or some other means of telling Sonar whether or not to associate a track with its folder when creating a track template.
 
I think the difficulty in implementing something like the above would be that there can be any number of tracks included in creating a single track template, and with that comes having to somehow be able to both declare and control that decision on yes/no for association with a track's folder (if present).
 
How would they best present such a dynamic mechanism, and where in the track template creation process would such a mechanism be placed?  (then there is the code to handle those association parameters to build into the insert track template process, without making the whole process too cumbersome).
 
Anyways - give the above some thought, and think about writing up a feature request for it.  Maybe it will make sense to them to do some sort of accommodation of it.  I suppose that would depend, partly, on their assessment of how valuable/needed is something like that, and then of course how much would be needed resource-wise to develop such a mechanism.
 
Bob Bone
 

It would probably be a lot easier to make the inspector not appear every time a track temple is inserted, and also to remember the bus colors that were intended for that track template ... both of which need to be addressed ... in my opinion.
 

IMO, an option to select an existing folder when inserting a template would be the most straight-forward.  For non-instrument templates I find it easiest to not use folders for templates and drag/drop instantiated tracks to a folder if I want them in a folder.

For myself, I generally create a track template to always use associated track folders, or will create separate track templates where the track is not contained in a track folder, for those that I want to keep out of a track folder.
 
For example, I have many track templates for each custom drum kit I have, and they all have a track folder and one or two audio tracks for each active drum kit cell, a midi track for click rhythms, another midi track for the real drums midi data, the various buses (toms, cymbals, snare, kick, parallel comp, etc.), and each drum kit piece's initial peak set to be at around -18 dBFS with its fader(s) at Unity.
 
I will always want the drum kit track templates to be inserted into my projects with all of the above, brought in with the track folder all of the drum kit tracks.
 
For things like guitar track templates, I always set those up as not being contained in any track folder as part of the track template.  I often will MOVE a given inserted guitar track into a track folder, such as into a Guitar Leads track folder or a Rhythm Guitars track folder, as appropriate, but that is done manually with a Move To step to place in a target track folder.
 
I may set up a set of track templates that contain one instance of Kontakt, 5-6 loaded instruments, and the needed audio and midi tracks, buses, whatever is needed, when I have a frequently used combination of instruments, like grand piano, organ, strings, bass, whatever, and I find that can be handy, but more often than not, I will manually load up a newly inserted Kontakt instance with whatever is needed for that particular project at that time, because that gives me all the flexibility needed for the project I am dealing with.
 
Ultimately, it all comes down to convenience and flexibility, with regard to track templates, and some of that will vary from person to person.
 
But, for you - perhaps it does make sense - for how YOU do things, so a feature request would be the thing to pursue.  :)
 
Bob Bone
 
 

BobF
IMO, an option to select an existing folder when inserting a template would be the most straight-forward.  For non-instrument templates I find it easiest to not use folders for templates and drag/drop instantiated tracks to a folder if I want them in a folder.

 
The only thing though is if you have a track that happens to be in a folder that you want to make a template out of, you would need to move the track out of the folder, save it, and then move the track back into the folder.
 

Magic Russ

BobF
IMO, an option to select an existing folder when inserting a template would be the most straight-forward.  For non-instrument templates I find it easiest to not use folders for templates and drag/drop instantiated tracks to a folder if I want them in a folder.

 
The only thing though is if you have a track that happens to be in a folder that you want to make a template out of, you would need to move the track out of the folder, save it, and then move the track back into the folder.
 

I would create all track templates (except VIs I always want their own folder) without folders, just like I do today.  Today if I want those tracks in a folder, a drag/drop them into the folder I want them in.  With the option I described above, I would pick a folder during instantiation instead of drag/drop later.