EMC Source M-codes pause motion

You may recall my earlier inquiry into the motion pausing to execute
m-codes issue.
Nobody had a quick fix for me so I decided to read through the
source files to see if I could isolate the problem. Since I am just
beginning to learn programming the do-it-yourself way I'd like to
get some expert advice.
Findings:
I read through the rs-274ngc files & did not see anything associated
with the m-codes that would generate a delay. I am assuming the rs-
274ngc files are what everyone refers to as the "interpreter".
I read emctaskmain.cc & found this to be the command sequencing
controller (I think). My understanding of how the m-codes in
question (m3, m4, m5, m7, m8, m9) are handled is; in all modes
except auto/reading (processing a file) these functions are executed
immediately.
Hypothesis:
If these commands are removed from the emcTaskCheckPreconditions
section & the emcTaskCheckPostconditions sections & inserted into
the auto/reading immediate commands section they will be executed
without forcing a wait for motion.

Is this anywhere near the ballpark? Are there other issues that
would be left open by this change such as messaging?

In other topics, does anyone have a flow chart or any type of aid
that describes the interrelationship of all the different components
of EMC? I have a copy of the source notes but they are too
microscopic in scope (no offense intended to the author(s)), they
don't describe the bigger picture. Perhaps an explanation of a basic
BDI default installation without all the uncommon/typically
unnecessary components described would be a good reference point.

Thanks,
Dean