Does M5 Break Blending?

Should I config and use an M63 to turn off the relay that fires the torch. Would that help give me a torch off with out the stop/hesitation?

%
g64p.001 q.001
f100
g0 x0y0
m3
g1 x4 y0
m5
g1 x8 y0
m3
g1 x12 y0
m5
g1 x16 y0
%

%
g64 p.001 q.001
g0 x0y0
m62 p0 ;turn on 
g1 x4 y0
m63 p0 ; turn off
g1 x8 y0
m62 p0 ;turn on 
g1 x12 y0
m63 p0 ; turn off
g1 x16 y0
%

15. M62 - M65 Digital Output Control

M62 P- - turn on digital output synchronized with motion. The P- word specifies the digital output number.

M63 P- - turn off digital output synchronized with motion. The P- word specifies the digital output number.

M64 P- - turn on digital output immediately. The P- word specifies the digital output number.

M65 P- - turn off digital output immediately. The P- word specifies the digital output number.

The P-word ranges from 0 to a default value of 3. If needed the the number of I/O can be increased by using the num_dio parameter when loading the motion controller. See the Motion Section for more information.

The M62 & M63 commands will be queued. Subsequent commands referring to the same output number will overwrite the older settings. More than one output change can be specified by issuing more than one M62/M63 command.

The actual change of the specified outputs will happen at the beginning of the next motion command. If there is no subsequent motion command, the queued output changes won’t happen. It’s best to always program a motion G code (G0, G1, etc) right after the M62/63.

M64 & M65 happen immediately as they are received by the motion controller. They are not synchronized with movement, and they will break blending.
Note
M62-65 will not function unless the appropriate motion.digital-out-nn pins are connected in your hal file to outputs.

Edit: That also sounds like I will need to reprogram all existing jobs because those M3/M5 jobs won't run as the new and2 inputs won't be satisfied. Not all current jobs *need* the torch off early.