I understand what you're saying vis a vis the relationship as peers rather than traditional heirarchy. I also appreciate that there are many use cases where for many, they're wanting to establish the higher performing protocol as the entry point for their own network. For others, like myself, I'm primarily utilising the VPNs as a means to take advantage of my American cultural roots despite living in a far off land.Right - usually you would set up a WireGuard 'server' Peer on your router as you have identified a requirement to safely/securely access your home LAN from another location via the WireGuard VPN-tunnel.
Correct - although it doesn't have to be a commercial WireGuard VPN provider it could be a family member's home LAN.
NOTE: Unlike OpenVPN, WireGuard doesn't actually have a traditional 'server'/'client' hierarchy - WireGuard Peers are deemed equal.
Regarding that, I engage with a large VPN provider (Nord) and had no problem with setting up the instances for udp, testing tcp, etc, to find out how everything performs. I'm not a linux savvy as I may have once been, but I'm also quite capable of digging into a terminal screen and dealing with things at the command line level, with some handy guidance. But, whenever I've tried (multiple times over the past year) to dig in and do the wireguard, connect it to Nord and have my selective routing for devices going through that.....the material that had been out there as guidance ultimately has had my eyes glazing over and I'm just not grokking it.
While a nice gui would be great, I'd also be happy for written instructions around those specific use cases. I also appreciate that it's my problem, and not the collective "yours", and people have other things to do. But should one of those appear, I'd be very grateful to be a test monkey to see how well I can follow instructions. I am interested as well with the why's behind and beyond a simple telling of "what to do"...