Once you design an empty project the way you want it, you can save it as a project template. This will save routing, mixer settings, preloaded plugins and mixer 1,2,3, and 4 custom designs.
Considering that you mentioned only view and visibility items, I would also rather consider using global workspaces instead of templates : they allow different layouts and tracks visibility settings for the MixConsole, among others. IMO, they are more practical to use on a daily basis, as you can save/update them quickly on the fly whenever you make a change, without bothering to create and reload a new template each time a change is done.
An alternate way of doing could be to use the four different mixConsole available but, well… There are only four.
You can actually create a macro to configure the mix console to an extent, but there are several settings that are not available in macros. I’ve also gone the template route to get a pre-configured mix console (templates are overall a good practice anyway), but use a macro to get projects that don’t derive from that template in the right ballpark
This ( • saving WorkSpaces • ) does not work ~ which is the reason for my posting… because based on documetation you would expect it does… yet… um, how would this be made work ?