Ahhh.
Most people who own a vacuum cleaner don't care whether the motor is a universal type or synchronous AC single phase type. They don't care about the number of poles in the motor, the metallurgy of the axle and bearings, etc etc etc. They care that they can switch it on and clean their carpet.
If you compared two vacuum cleaners that looked and sounded identical, and then tried to say the one with the universal motor was much better than the one with the sync AC motor, most people would just shrug and let you get all religious ranty but stop listening and not care. They're the same. If you then tried to tell them that one had an offset gripley discombobulator simplexed to its axial offset vortex migrator they would probably just nod, smile and walk away.
Yes, people need to know that there are options. But if you need to go down to the guts of the architecture at a software engineer's level of understanding to see the difference then, for the people using the software, there effectively is no difference.
The processor workload of running a toolpath, even with on the fly curve matching and acceleration lookahead maths going on, even doing floating point all the way down, is utterly insignificant in the scope of modern microprocessors. If the machine has been built and OS installed purely for the purpose of running the machine control software, then it's idle 99.9% of the time and any OS will be pretty reasonable in terms of lag and latency. If the hardware is fast enough and the load low enough, pretty much anything approaches an RTOS in its external behaviour.
Windows is not a "real-time system". Mach3 is an application, noth part of the OS. It comes with some drivers, which are not part of the OS. Installing those drivers lets them run under supervision of the OS with a little more latitude and priority, but they are not part of the OS. Throwing hacks in at the driver level can make it a little less laggy and a little more deterministic, but it's still not a real-time system and never will be.
Linux is not a "real-time system" either, although I understand it can get extremely close with the right kernel mods. The ones LinuxCNC apparently uses in its build - and it looks like LinuxCNC is the full real time linux kernel with the CNC apps included in the install package.
So, from a software architecture/engineering point of view, LinuxCNC is by far and away closer to a RTOS but, as long as it works, no-one cares. Well, apart from those members who are bored and have enough computer science knowledge to be dangerous and really just want to have a d*ck swinging competition. I'd back this up with a CV of software blah blah blah but really don't care enough to argue. Sometimes it's easier to just say your piece and let people who disagree be wrong.