Yes, that's a great use case for it. And yes, it's a great tool I use often.
But ssh tunnels have their use case. Specifically that wireguard, in it's implemented form, requires a server and client. Routes all layer 4 traffic by default, and must be configured. Ssh is pretty much already and always configured, and initiated client side with pre-installed client software on the big 3 operating systems. SSH lets the client initiate a remote or local tunnel and control the traffic type. Things you can kind of hack on wireguard with ip tables, is just built in to ssh.
SSH does also support chachapoly now btw. I require it for my sftp customers.
Both have a use, but when people call me up and want a quick way to handle the tunnels with higher level of security by default, ssh is a great choice. Can be done in a few seconds on the terminal with systemd.
