The "run loop" hooks into the existing browser's event loop in order to coalesce side-effects. This is exactly the same thing that the browser does when you make a number of changes to the DOM in an event handler.
You can turn that off if you want, personally I don't miss much of it.
As for the even driven stuff. Not sure what you mean by that, the run loop is not to dispatch dom events but to settle the bindings asynchronously (with the benefits of not triggering multiple changes for the same property within the same run loop and having a comprehensive pipeline to get data on the screen).
The "run loop" hooks into the existing browser's event loop in order to coalesce side-effects. This is exactly the same thing that the browser does when you make a number of changes to the DOM in an event handler.
There is nothing strange going on here.