I too am encountering this bug. Strange thing is, I uninstalled litestep a couple weeks back and reinstalled it recently, and it is only occuring with this freshly installed litestep. Maybe its a particular version doing it? I'm using the LiteStep 2.1 (Omar) build at the moment, not sure what I was using before. Is there something in the registry or a startup.ini sort of file that we could edit which would disable this wait for load delay?

Instead of arguing lets see if we can't help get this fixed ;)