The way LightBurn works internally, when you click ‘Start’, the entire GCode for the job is created, put into a buffer in memory, and the system begins streaming it from that buffer. This means that you can close the file, open a different one, and start working on the next thing without affecting the current one.
Many of the things that you can change in LightBurn, like the dither settings, DPI, etc, make very drastic changes to the content of the GCode, so they would not be at all simple to update on the fly.
Power and Speed can now be adjusted in the Move window while the job is running, but those changes are only active until you stop the job, and don’t affect the settings in LightBurn - the controller doesn’t have a way for me to know what the new settings are, because of the way these real-time controls are handled by it.
What most people do is use a generator or a set of samples with different settings to run test swatches, and use those to get the initial starting point set before doing the fine tuning. This is a good one: Lightburn PowerScale Generators - O2 Creative