I was a bit brief in my request so I suspect we are on the same page, more or less. what i was trying to describe was a button that I could click in CM to save way points along the way. I get that i will not catch the mistake in real time but If i am paying attention in my lazy style, I may click the save this spot button when I am happy with the progress that has been made after 30 minutes or so and again after a hour out of a 1.5 to 2 hour job. The idea being I could start again from there rather than start over. I think this deals with your issues with my original description.
This waypoint feature would not have to nab that exact line of code but rather find the appropriate spot within recent history that would make a good stop/start point.
Adding to that idea. It would be nice as you say to know where in the process CM is bot in terms of process and in terms of line of gcode. I know this is a tall order on the process side but it might be possible to generate some sort of text string in the gcode on the meshcam side that CM could display as a means of giving status. What line of g code would be good as well.
While paused, it would be great to be able to check the zero location as well, then go back to where you paused. This would be extra helpful to check to see if the nomad is only slightly confused or completely lost before resuming operation after a fault.