you are spot on with this. This was our initial design direction. However, the ListView already supported (albeit incorrectly) endless scrolling and press to load more. Introducing another widget with the same features working in a different way would be even more confusing.
Unfortunately, the databound event has a special role when the widget is MVVM bound. Triggering that when scrolling would cause a significant performance penalty (as all DOM elements would be re-iterated). I do understand that this results in a certain level of inconsistency – this is purely due to implementation details which we can't change without causing big breaking changes in the current behavior.
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI