Generally they do have development versions daily updated and built and tested under the hood. Generally they do provide support and feedback to these software by bug reports or even with changesets.
But they are not slow.. most of the time they do work out of your eye sight.
I can bet some admins are trying to see if mod_lua can be a good replacement for the current configuration.
For myself I do not like it to happen. Because most of the deployments of apache are huge and this will break too many things.
And yes, if it's working do not change it :)
(edit: gramer and typo corrections)
Unless you've got an employer or client that can afford you for an additional 20 hours for each major change, everyone involved just crosses their fingers and holds their breath. I've never been an admin in an environment where there was adequate funding, though, so maybe it's just me.
Anyway, I typically put off upgrades and new installs that affected old servers (new apache modules or whatever) as long as possible.
Edit: this is why I just code, now. It's easier to write stuff that works than to find the magic this-THEN-that incantation to make someone else's stuff work. ;)
I bet you tested most of the changes on your own time and on equipment when possible.
For myself I do.
Point being, I think you're right and I think my initial reasoning was wrong. But all the same, a little mailing list discussion generally doesn't hurt.
If it catches on, then you have a replacement to the current config syntax.
That said, in my experience, admins are slow to change. There are still sites running Apache 1.3 out there.