I'm afraid upgrading to 2.5.2 is the only way to prevent it right now (the error is timing related so it can or cannot happen to anyone at any time).
Yes, this would be nice. Unfortunately sequencing with a multi-threaded application is mildly complex. Understanding of the logs by end users was never one of our goals (though some have taken to them like a fish in water). We did, however create user-facing logs via the notification system. This is a much more readable log (but of course, also lacks in its description of errors).