Hey Mike,
Did you ever start a new thread? I am here to also vote that "Anything that causes a 'Command has been aborted' results should be a severity > 10."
I found this thread while investigating why our inserts were seemingly succeeding and yet returning a row-count of 0. I can see reasons when the results might be 0 rows, but none of them would include a "Command has been aborted" statement.
For my own education, it's too bad that we cannot know what clients this would affect as I would be very interested to know who likes it the way it is and what conditions they have where the current state meets their needs. Anyone that wants to continue on processing in an overflow can easily try-catch their way to success, but I have to add a lot of machinations in order to get it to fail as I expect it should.
