1) Put "Start without debugging" into the Right click menu for a particular project.

This is just smoother than "Right click a project, select "Set as Startup Project", Use Control+F5 or Debug | Start Without Debugging", and then go back to the project that you want to debug and Right click to "Set as Startup Project", and then do F5 to debug.

The current behavior is clumsy when you have two projects that interact such that you need to run one without debugging first, and the other with debugging second..

This was also suggested in 2006:
https://connect.microsoft.com/VisualStudio/feedback/details/111466/right-click-start-without-debugging#tabs

2) Make "Start without debugging" and "Start debugging" consistent for console programs at termination.
"Start without debugging" keeps the console program visible after the program stops.
"Start debugging" closes the program without letting you see what happened.

I don't think there is a good reason for this divergent behaviour. It is annoying to put a break point at the end of the program to be debugged each time, and I suggest that Visual Studio always stops after a console program has terminated to show the result.

I suppose you could make it optional in the project properties too.