This problem can be resolved by the newly introduced property ShowScrollPositionIndicator which indicates whether the ScrollPositionIndicator will be shown while deferred scrolling. It will be available with the next LIB (version 2018.3.1029) expected on Monday, October 29.
This is a very important issue for us - in several areas, we have RadGridViews that display maybe 12-15 items at a time, out of a possible 5000. When the user scrolls using the scrollbar, what should happen is that the client should query the server for 15-20 items around the area where the user released the scrollbar so it can populate that portion (i.e. what's in the viewport). What it's actually doing is hitting the server for every "page" between where the user started and where the user ended. So if they have a viewport of 15 or so, and scroll from the top to halfway down, it is hitting the server for 15 entities several hundred times. This kills the app and also the server.