It would be
very expensive for ISPs to implement this kind of thing.
So Occam’s Razor makes me doubt it. ISPs do all kinds of tricks to make speed tests work well, co-locating, prioritising that path etc. But I don’t think they’ve complex profiling equipment that slows everything, then removes the slowdown when they see DNS/SNI for speedtest, then apply it again after.
Also been working for ISPs for 20+ years and never heard of it. Only exception may be in cellular with their fancy PCRF boxes, but even there I think it’s much more common to throttle one class, and not another, than to slow everything but switch the throttle on/off if you access a particular site.
If this is true you could easily game it by running speed test all the time. All you gotta do is throttle bandwidth to the speed test servers yourself somehow (so the speed test goes slow and doesn’t eat your available bandwidth.) Then you’ll be permanently in the “they’re doing speedtest give them full speed” category.