Doesn't seem related though, since if you ran a public server from home, that server would appear through your public facing "Internet" IP rather than its intra

Doesn't seem related though, since if you ran a public server from home, that server would appear through your public facing "Internet" IP rather than its intranet address. It might make some homelab setups slightly more annoying, though. FWIW, I do the same as the article for my home network: I hijack all DNS requests from intranet devices and respond with corresponding intranet IPs. Externally on the internet trying to resolve those same (sub-)domains would lead to the public facing firewall. This makes it so I can manage stuff like NASes and IoT stuff fairly easily regardless of where I'm connecting from. Luckily none of my stuff really depends on making cross-boundary requests between intranet and internet services (it's always completely internal or external) so I should still be OK.