If you use IPv6 globally routable addresses for your services you can avoid all split horizon DNS, NAT, hairpin, etc. With the magic of IP routing and maybe some custom wireguard route advertisements your packets will go through the shortest path wherever your client hosts are.
If you drop the "from anywhere" part, you can set up a pihole with a static address that you can use from within your LAN, without any involvement from your ISP.
Apparently this message used to be common when GDPR first came into force.
Also, I love that the response code is 451. It's meant to replace a generic "404" for content unavailable specifically due to legal reasons. And of course 451 is referring to Ray Bradbury's book of the same name.
It seems a common reason to set up a frontend is for family use. I suppose that is a logical extension of designing a system for its users - if someone wants to use it a certain way, they get to use it that way.
If you use IPv6 globally routable addresses for your services you can avoid all split horizon DNS, NAT, hairpin, etc. With the magic of IP routing and maybe some custom wireguard route advertisements your packets will go through the shortest path wherever your client hosts are.