OpenVPN: how to bypass from router itself

I have an openvpn client installed on OpenWrt router, and all devices connected to the router leverage VPN connection to connect to wan.
How to configure router to bypass vpn from router itself?
Case: I want to download another VPN configuration if current VPN server is unavailable, hence require a non-VPN connectivity on router.

You need to make a rule for the router itself to use a different routing table, which will have default gateway via your ISP.
Or you can use Policy Based Routing package.
Or you can default the ISP gateway and use the VPN gateway for the hosts only with a rule/route set.

@trendy Apologies, network routing is really my weak spot.

Basically, I have an OpenVPN client configured on the router (Linksys 3200 ACM).
I use https://dc502wrt.org/ firmware, and right before the last release everything worked well.
However, latest snapshot vis distupgrade was unsuccessful (problems with wifi), and I had to reset settings. I can't rollback to the previous release, as dc502wrt keeps only the latest snapshot, however I had a configuration backup. diff'ing didn't show any changes in /etc/config/network, hence the question.

What I currently have is the following (and 2 routes with 0.0.0.0 as destination seem suspicious to me; 192.168.55.1 is the proper gateway):

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.8.2.1        128.0.0.0       UG    0      0        0 tun0
0.0.0.0         192.168.55.1    0.0.0.0         UG    0      0        0 eth1.2
5.253.206.91    192.168.55.1    255.255.255.255 UGH   0      0        0 eth1.2
10.8.2.0        0.0.0.0         255.255.255.0   U     0      0        0 tun0
128.0.0.0       10.8.2.1        128.0.0.0       UG    0      0        0 tun0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 br-lan
192.168.55.0    0.0.0.0         255.255.255.0   U     0      0        0 eth1.2

The preferred routes are 0.0.0.0/128.0.0.0 and 128.0.0.0/128.0.0.0 via tun0 as more specific than 0.0.0.0/0.0.0.0 via eth1.2