Point I was trying to make is not to debug the machine configuration but instead question whether or not you actually need it, it seems to be in early stage of development and has issues.
There are users that need to post same file for different machines, so they need those machines to be correctly configured and machine configuration itself needs to be bug free for concept to work.
If all your work is done on same machine, for all practical purposes, you can just ignore it and get on with making parts.
Subsequently, if the machine configuration does work, it can be used in simulation to uncover potential crash issue not visible in simulating tool path alone.
For instance, you can have fixture, bolts and other obstacles to avoid where simulating crash costs nothing as opposed to having to determine danger of crash as you run the tool and make chips, but it is still theoretical assumption based on all things being correctly interpreted.
In my view, dry running program in machine is trustworthy step before making a single cut, while machine simulation can save you time, one wrong variable in its configuration and simulation process can cost you a bundle if you trust it without dry running program and physically ensuring crash free run.
At this stage, I have no use for machine configuration in any of my Fusion files.