This is something that exists on both GPUs and displays, and must be something at the firmware level since, at least on the GPU side, it can exist on both Windows and Linux even for Intel and AMD GPUs (which obviously use completely different driver stacks between Windows and Linux due to the former being “absolutely proprietary” while the later is just mesa).
Luckily, as displays have move past 1080p 60Hz, it’s much less of an issue nowadays, but it definitely isn’t something to just sweep under the rug.
There’s a giant thread on AVSForum regarding this very topic, though the first post is quite outdated so you should refer to the last page where I made a post covering modern work-arounds: