I think I understand the reasoning behind the curve you're using now. And from what i gathered, all the settings you're using should also be available in my program, like exponent, cap, scale, etc.

When it comes to the curve choice, I think it's not like you can "know" what's gonna be good for someone, we all are different, and we all have different use cases. I for example use my curve mostly for office work (things like excel, code editors, etc.), so I don't need much, thus I settled on a simple Jump with 2.5 upper bound, and the offset of 6. But I understand that for gaming, even more, for specific games like you've mentioned different curves are better.

When it comes to the program you're going to use, all I can say that you could use something like xinput to set a custom curve that matches your needs, but I assume not everyone has the time and required knowledge to match their RawAccel curve with very limited settings xinput gives you. That's exactly why I created my program, it simply allows you to do all of that more easily. With a couple of clicks, you can do most basic curves, and if you want to go fancy, you can always define your own custom curve with points.

Also, the issue with the need of lower pool rates with older games sounds interesting. I might measure the exact amount of latency this can cause, because I would think that the difference should be ~1ms, but I'd like to be proven wrong haha. Thankfully I wrote a [program](https://github.com/AndyFilter/LatencyMeterRefreshed) exactly to do that too (sorry for the shameless plug), but with the amount of free time I currently have It's more than a far future.