Interesting comparison. I believe that to make sense of it, you'd need to display the NUMBER of bytes read, and not only the RATE. This way, we can be sure this was read "twice".
As far as I can see, using Process-Hacker , it reports the correct size in the disk stats->hashing, but only HALF the amount being read by uTorrent process. I guess the other half is being "correlated" to he OS, so I believe you are seeing Windows caching/paging "helping" out to split the READ load... just not very efficiently as before.
https://www.imagebam.com/view/ME7QPTJ?full=1