we set this policy (value=1.2) via GPO in our enterprise and it is VERY effective to block user override for old/bad TLS.
https://learn.microsoft.com/en-au/DeployEdge/microsoft-edge-policies#sslversionmin
when I use EdgeChromium v92 to test browserleaks, it show TLS1.0/1.1 disabled, except if I enable the IEMode feature on that browserleaks page, if I do that, TLS1.0/1.1 are enabled because IEMode/IE11 currently allow old TLS by default.
I manage an enterprise corporate desktop ecosystem and we have a couple of very old intranet webapps which still use old TLS, we use IEMode to allow those.
So, I don't trust that reference site you quoted (Fourth/hotschedules), I think its simply wrong or very outdated, as some of the feedback on the site itself suggests.