This capability would cause an exception to be thrown by a driver when it gets a serious error preventing executuion. A outer catch could cartch these and write them to a driver test output window along with stack data.
In addition when running LINQPad under debug the debugger could be configured to break when an exception is thrown - although there is limited src available - this would still allow a developer to see stack traces etc and gain insights into what might be wrong.
When this new feature is disabled LINQPad would behave as it does now.