Too bad you can't use LAN to work from home
DSL & Cable encapsulates Ethernet. City-wide networks are again Ethernet. In fact, everything is Ethernet with some routers between.
So, you're actually using a mixed-carrier Enthernet LAN with a couple of NATs in the way. You can build another LAN on your LAN with VPN, too.
That was my point responding to OP. We actually progressed and we are facing new challenges.
A country wide router still can stay in service for a decade. Residential FTTx installations consist of a TelCo class switch, maybe a router, compact DSLAMs if you have DSL service and a couple of fibers in, tens of fibers out for FTTH customers.
It's faster hardware on the same stack. Nothing more, nothing less.
...and, oh, link-speed (transparent) DPI equipment in key places for lawful interception.
...and possibly a small DNS server (or a hosts file somewhere easy to get).
That's all you need.
If you want to navigate via IPs only, you can do with a DHCPd.
Depends on what you consider "work from home". You might not be able to chat with your co-workers without a WAN connection (unless you go really old-school and use a telephone), but you can for instance develop software from home without any working network connection (and git makes it easier by allowing you to create commits while offline; see also the "git bundle" subcommand). I've done so occasionally when the Internet connection goes kaputt.