Of course, if you put a gun to my head I can work around that issue too: defer the cache update by keeping a local list of updates-to-process. Implementing this so it gets tracked across profiles properly is of course not trivial.
"And what if the application is stored on a network so it's not updated locally, and someone logs in from across the world to use the upgraded version of the application?"
Then push the update to the domain controllers.
"This feature started off at -100 points, care to guess how far it's come along since then?"
Shut up, imaginary version of Raymond.