I find it really hard to believe your RAM could eat 60 fps, is your fps still that low if you pause a replay on a full grid start, hop into shift-u camera and look around at all the cars?
Not the end of the world, but not very good (16% :zombie, might just be your link to that particular speedtest, most online/web tests are incredibly incorrect for obvious reasons.
No problems with T for me, few hours yesterday, 80 minute run in an endu race just now, no disconnections or lag at all.
Logic suggests that your CPU is falling behind when there's more cars to calculate physics for (more cars in view), try pausing a replay of a full grid and look at the difference in fps, that difference is probably close to the amount of fps sucked away by physics calculations.
Got the patch, drove a new PB on Kyoto GP / XRR, struggled at Blackwood in the XRT. Summary, race car behaves more like a race car, road car more like a road car, great.
Have you tried recording "full size" and lowering your LFS res? The more pixels for fraps to look at - even if it only saves half - will increase the workload.
World of difference, mplayer can be configured to your liking (and beyond), nkpro can hardly be configured at all.
In essence mplayer and VLC are basically the same thing, mplayer is less bloated by default while carrying a few million options if you really want them (there's even GUI's!), it's a bit faster and easier on cpu, and it plays anything and everything, it also has an encoder featuring pretty much the same amount of options.
It also works by just dragging and dropping a file onto the .exe, so it's not really that hard to use.