IMO, Marlin suffers from its history as 3D printer firmware, with many compromises and optimizations that make it … suboptimal … as general-purpose CNC control firmware. If you plan to dive into G-Code, you should use their definitions:
https://reprap.org/wiki/G-code
GRBL implements the more standardized LinuxCNC G-Code dialect, with comprehensive documentation:
https://linuxcnc.org/docs/stable/html/
In general, unless you know an option is supported, turning it on tends to cause heartache & confusion.
AFAICT, G-Code clustering is only in Smoothieware and a few other 32-bit microcontroller dialects.
Practice on cardboard until you know what happens.
I use cardboard until I know how both the machine and my layout will behave. This tends to reduce the number of expensive surprises, with the side benefit of making them even more surprising.
That dialog should be amusing.
Having watched this play out a few times, I expect the answer will run along the lines of “Sure!”, with any & all problems blamed on LightBurn, until you prove otherwise, at which point they’ll (say they will) pass it on to their tech staff and you’ll experience a complete signal dropout.
You could determine whether Creality makes the complete firmware source code for your machine available, as they should under terms of the GPL:
Then you can recompile it and do your own fault analysis!