OK. Took me a couple of hours and some more research on the M10/M11 commands, but here it is what is working for me.

Preconditions:
1. I already had my laser "fire" confiurged to work with a spindle relay on Output #1.
2. It was working well with M3/M4 and M5, but had the 500ms delay at the beginning.
3. M3/M4 turn on the spindle (Laser for me) immediately when encountered.
Changes to make M10/M11 work:
1. Realize that
M11 is
ON and
M10 is
OFF (intuitively backward from the M3/M4, M5 combination.
2. You have to explicitly specify the Output # (M11P1 turns on output #1, M10P1 turns off output #1)
3. M10/M11 do
NOT execute
until there is a
subsequent G0/G1.
That 3rd item is what took be a couple of hours to work out. I kept testing with the direct input and my relay never fired because I was not following with a movement command.
So, my code needs to read as follows:
N001 G0 X0.0 Y0.0
N002
M11P1N003
G1 X1.0 Y0.0
N004
M10P1N005
G1 X1.0 Y1.0
N006
M11P1N007
G1 X0.0 Y1.0
N008
M10P1N009
G0 X0.0 Y0.0
N010 M30
This draws two parallel lines, one from 0,0 to 1,0 and the second from 1,1 to 0,1
Important: Notice line 9 - if you don't make this final move, your M10P1 will not occur, so the laser will not shut off.
ALSO, if line 9 were a G0 or G1 that did not actually move the head, then there would be a 500ms delay in turning off, resulting in over burn at the end.
In summary
M11Px (x= output number) turns my laser ON, but NOT UNTIL the subsequent Movement command.
M10Px (x= output number) turns my laser OFF, but NOT UNTIL the subsequent Movement command.
The Movement commands that follow the M10Px MUST actually move the head, or there is a delay in turning off the laser.
Like most things in life, seems really simple, once you know the answer, but difficult as heck until you do!
My personal philosophy is once again proven - "
Whatever we ardently desire, sincerely believe, vividly imagine, and enthusiastically act upon MUST inevitably come to pass." (Time, effort, and passion make all things possible!)