It’s mainly about the optics. What you’re getting now is calculated on a per-millisecond scale, which works well only if you can guarantee that users were scheduled in each of 60,000 intervals in an hour.
Using pmActiveUeDrbSamp instead provides an accurate average, because it removes the TTI intervals where no user was scheduled in an hour.
The difference will be more pronounced in daily stats and in hourly rural stats.