This isn't the fix you were asking for, but modifying templates is probably your best bet and this is kind of what templates are for. So load a template, change the outputs then save as template overwriting the original - or save as new. Do that for the templates you want. 
 
Personally, I only use my own templates which I have created for my setups - including non standard hardware routings. It's quick and easy to set up a template and it can be modified at any point or used to seed a new template with all my current settings in place. I also have one of my templates set to default so it creates a new project that's ready to go every time I start Sonar.

That was my first thought.

Instead of trying to change this way, simply create a template as you wish and set it to default...

Yeah, I use templates all setup the way I like it for new projects.
But I did a quick one off for someone and used the Basic template which I think might be the default and that's when I realized I was annoyed. :-)
 
When BandLab gives us an update, and they said they would, those cakewalk templates will get clobbered and set back to default. Then I'll be annoyed again.
 
Don't you think the output should be a global preferences setting, or use what output is set in Playback Timing Master?

This is why I use a custom project template folder path. The installers always used the default location leaving any custom template folder alone. This let me pick whichever I wanted from the ones included with SONAR and create my own without worrying about them getting overwritten by an update.

Since the new DAW will not be called SONAR, it will probably use new folders and registry entries unrelated to SONAR.

If you create your own "basic" say as a renamed basic (ie mybasic.cwt) then set it as your default, it will no longer affect you when updates overwrite the factory...

No kiddin.
 
Okay, I'll try that.

Notice the "set as default" button for templates and all will be well in the garden...

Keni
If you create your own "basic" say as a renamed basic (ie mybasic.cwt) then set it as your default, it will no longer affect you when updates overwrite the factory...

Yes, the templates that come with Sonar do get overwritten when updating so if you change those and save them with the same name, they will be reverted. Changing them and saving with a unique name will ensure they don't get overwritten. I back mine up too so if the poop hits the fan I can reinstall Sonar and put my templates back in. Actually, templates are incredibly useful as they do save pretty much everything.

While updates to SONAR templates are unlikely, the only way to guarantee they would not be overwritten was use a custom folder. Regardless of the name chosen there was no way to claim for certain Cakewalk could not overwrite the file.
 
I also use a custom folder for drum maps to insure only the ones I want are displayed.
 
Where a custom folder cannot be specified (ex. track templates) I add a custom folder created with a directory junction. As much as possible, I place all customizations in a single directory tree. This makes backup, updates to new versions and re-installs much easier not to mention Cakewalk never wrote into custom folders.