Hard to say with the one route. Internet just stops on this one node? Or are other devices affected? Have you checked the routing table on both the Route10 and your VPN_PC? That said, if there is an alternate way that might be more likely to just work (read below), and if interested, no need to answer these. IF you want to check any of this, but are unsure of commands, please let me know.
So far any time someone has asked I’ve pointed them to @dalewhlrr’s post HERE. You don’t need the whole thing, but the WG+routing segment+firewall reload (see HERE). There is a heath check too, which is nice, but technically optional. It requires some modification, but maybe this is quicker/easier to get up and running? For me, I view it as why re-invent the wheel when there is a working solution that already exists.
If you opt to go this route, I would delete or disable the old/existing client config first as you want to fully provision it from the details set in the post-cfg.sh that you’d be crafting. If possible, download the text config file from the VPS provider, and then you can open it in your preferred text editor and most of the information required will be right there.