Thanks Brundle, I did a search and found it has come up again and again. I know that it has been this way for some time, I was hoping maybe a rolling update would have captured this.
I was just sitting here experimenting while thinking of a workaround... I saw that multiple sends don't necessarily kill cpu per se, so here's a thought. Track template.... blank track, add four sends to a generic buss (in my case NULL BUSS) since that's the max that can be seen without the up/down arrow.
Make sure the OUTPUT of the NULL buss is set to NONE. This idea gave me an error that I don't want to hassle with every time I add a track. Make sure the OUTPUT is set to anywhere BUT turn the VOLUME DOWN. Turn the sends all the way down. The sends are instantiated and doing nothing and sending a big fat nothing to nowhere. Lots of double negatives, but I hope I get this across. Export the track template. I called mine 4 sends.
Insert -> Track template -> 4 sends. Leave the PREVIEW buss alone since nothing is going to it or leaving it anyway. As someone needs a verb or headphone mix, you can switch the SEND destination and the SEND amount stays all the way down. Aha--- one more trick.... Hide the NULL BUSS then export the track template. then when you add from track template, NULL BUSS is still hidden.