Overlapping wireguard subnet with 128.0.0.0 genmask

[basiceconomics]

I'm experimenting with a linux home grown VPS. It has wireguard configured and several clients connected to it. I then use openvpn on the same server to connect to a VPN provider. Both individually work fine. however, the wireguard subnets fall under openvpn's gateway genmask (128.0.0.0), and even though the wireguard subnet is a /24 and more specific than the openvpn subnet, when the server connects to the vpn provider it looks like the openvpn genmask is stomping on the wireguard subnet and remote wireguard client connectivity disappears.

Pre-openvpn
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 x.x.x.x 0.0.0.0 UG 0 0 0 eth0
10.100.8.0 0.0.0.0 255.255.255.0 U 0 0 0 wg0

Post-openvpn
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.123.x.x 128.0.0.0 UG 0 0 0 tun0
0.0.0.0 x.x.x.x 0.0.0.0 UG 0 0 0 eth0
10.100.8.0 0.0.0.0 255.255.255.0 U 0 0 0 wg0

I've attempted the following individually in the client config but no dice:
route-metric 10
redirect-gateway block-local
route-nopull

I thought i could also find a way to reduce the genmask size so the 10.100.x.x network isn't a part of the openvpn subnet 10.123.x.x 128.0.0.0 but have been unable to find out how to get that done.

the last resort will be to reconfigure the wireguard tunnels to a different, non-conflicting subnet, but now i'm stubborn and want to figure this out like a good nerd. appreciate any help.