I saw this excellent checkbox to put all outs from synths in a folder.
 
And felt, why not have a field for number of outs to create as well.
 
Now creating All usually are too much, creating 32 stereo outs every time.
And then go through and delete half or most of them.

That would be handy. In the interim, I have found track/project templates a good solution for setting up synths with multiple output.

Good call, I use that too.

+1 on the Track Templates, they save me hours and hours over time - looks like magic when you create and populate a largely empty new project in front of someone.
 
With a few mouse clicks, I get a track folder, an audio track for each drum kit piece, a drums midi track, and an instance of Battery 3 - with a loaded custom kit where each kit piece is sent to its own audio output channels.
 
While the ability to specify the number of outputs to set up as part of the Insert Soft Synth dialog box might be helpful, wouldn't that only save you from having to use a single extra mouse click to launch the Insert Multiple Tracks dialog box?  (I may well be missing additional considerations here, so I am posing an honest question here).
 
To be quite honest, for multi-timbral synths, which is what this request is about, I do use the Insert Multiple Tracks dialog box to insert both audio tracks and midi tracks for a given instance of such a synth, like Kontakt.  It gives me the ability specify the number of both audio and midi tracks to insert for the synth instance, and also lets me choose what synth port to assign any inserted midi tracks to.
 
Anyways, that's what I do.
 
Bob Bone
 

When I first read this I thought yes, good idea. I always delete tracks after adding Battery or Philharmonik . But after thinking about it, it's not really going to make a big workflow difference overall. Think of the total hours that you spend working on any single project. The time taken to insert a softsynth is hardly significant in the scheme of things. If we need time-saving enhancements, they should be applied to features that get used repeatedly in a project.