My observation....
The channel list shows actual data value updates and displays the last received value. The chart is always interpolating between points. This becomes very apparent when someone is logging way more stuff than they should be. An item in the channel list will might only updated once every second or 2 seconds or whatever, but the chart will show the data always moving-- it's just interpolating between the last and next data point.
I wish VCM scanner gave you a bit more insight into what "buckets" were being used and the expected polling rate or priority. But I also understand this gets really complicated because every ECU is a bit different and this probably gets very complicated from a GUI standpoint.
I'm most familiar with my Gen3 LS and thankfully its pretty simple but I've played with this extensively.
I know Gen3 LS has buckets that are 6 bytes and in a cycle you can poll 4 buckets at a time. Each cycle is around 10hz, so 24 bytes at 10hz.
What I did was set the request logging rate/priority to 10hz for 18 bytes and I set 12 additional bytes to 5hz.
Basically every cycle, the 3 buckets/18 bytes are polled every time and the 4th and 5th bucket alternate cycles, resulting in around 5hz for those.
It was tedious to set up and make it work, but it was important to me to get max possible speed on data that really matters when doing things like VE tuning, etc. That export to csv trick does help shed light on what's really going on too and getting the data rates you want.
Sorry long reply. Just sipping my morning coffee lol.