"Most websites do not work with TLS v1.2 anymore."
This has not been true for me. In fact, using a TLS proxy I have tried to force TLSv1.3 for all sites and a large number, possibly even the majority, still use TLSv1.2 and will not accept TLSv1.3.
If using old software/computers, one approach for dealing with changes in TLS is to use a present-day TLS forward proxy, bound to localhost address or running on a relatively recent computer on the LAN if necessary. This way, one does not need to do any encryption using the old software/computer. The proxy converts HTTP to HTTPS.
This has not been true for me. In fact, using a TLS proxy I have tried to force TLSv1.3 for all sites and a large number, possibly even the majority, still use TLSv1.2 and will not accept TLSv1.3.
If using old software/computers, one approach for dealing with changes in TLS is to use a present-day TLS forward proxy, bound to localhost address or running on a relatively recent computer on the LAN if necessary. This way, one does not need to do any encryption using the old software/computer. The proxy converts HTTP to HTTPS.