The MCR instruction is frowned upon, please achieve what you want to achieve some other way.
Has anyone seen one used in a program not in an educational environment?
To expand, the MCR is annoying, because you can't use cross reference to find out how a tag is being controlled. We all learn about it because we have to be able to troubleshoot a program with it in, but we try to be nice and never put an MCR in, just for our colleagues who might be out late troubleshooting our code. There are also weird things with subroutines and AOIs, because the end of a routine will set the MCR back on.
A de-energised MCR does not stop the code from working. It just makes the rung condition false. So for example if you had a TOF that would otherwise be on, its .DN bit will stay true for the preset time and then turn off.
If both of the MCRs are de-energised, then all of the rungs after the first MCR instruction will be false. Usually the first one is true/false as needed and the second one is always true.
The most standard way of replacing an MCR zone is to turn a bit on to enable the zone (eg with an OTE instruction where the first MCR instruction would be), then use that bit in an XIC on each rung that needs it.