Really?
Yes :)
Also the "use iterative rendering" how about if you just want to stop the render you're currently doing because you forgot to do something such as maybe not changing the file output to a different one and then because you're tired as.... you forget to hit cancel (which I know works correctly lol) instead of stop.
Well, you can also format your hd accidentally when being exhausted :) If you use iterative rendering, pressing stop or cancel, both will not save anything at all. The only difference ist that in case of "stop", corona would do prostprocessing stuff like denoising. If you render regular and press stop then -yes- files get saved. It's the fourth stop condition besides noise level, time limit and number of passes if you like to say so. And in case of animation or multiple frames, rendering continues with the next frame after pressing stop.
But usually when you start a render and the main output file exists, you get a warning box anyway. So the only dangerous situation is that one you obviously had: to use production with output unticked and having render elements active. You do not get overwrite warnings in this case, that was happening to you (and me two or three times btw. when not using embedded REs in EXRs/CXRs as output).
Just in my opinion it seems a little strange when telling it to stop rendering and you don't have "save file" checked that it saves the file.
Main output and render elements are considered to be two different things in Max, "Elements Active" in render elements would be the equivalent of "Save File" in Common tab.
Good Luck