So I gotta say I agree mostly with your views on exceptions Garry. It's important to understand what is happening and why it is happening. For warnings this can mean you analyze it, understand what the warning is saying, realize it does not apply to what you are trying to do, and so you suppress it in that specific case, though for me this is rare. For an exception something is clearly wrong that needs to be fixed.
However I think in a release build it may be desirable to try and keep the game running. Lots of frameworks take this approach. Unity... JavaScript... PowerShell (by default).... uh... Visual Basic....
I think it should be ultimately up to the developer. PowerShell and VB let you turn on or off this behavior. It may make sense to add a project setting in s&box for this as well. Maybe for in-development works you want it on (or just break to debugger when an exception is hit, like with .NET programming with VS) and with a published gamemode it's off, since presumably any errors by that point were unanticipated and you should at least try to keep going if at all possible.
Personally I would want to see and fix all errors in my code but I can understand there is situations, especially in production, where you might just want to cross your fingers and try to power through.