While it might have been "working", it was unreliable. Routes were added to the main table, and copied to client tables, which means you might sometime have duplicate, or missing routes.
Your current problem is probably that each client table ends with a default route going through the default gateway, which prevents you from matching multiple tables. A temporary workaround would be to delete the default route from the client table at connect time, through an openvpn-event script. I will experiment on my end to see if this works as expected, and if so, I will change it in the next release so that when Redirect Internet is set to "No", instead of adding the default WAN gateway, I won't set any default gateway to the client table. This should in theory allow the RPDB to continue on with the next table (the iproute2 documentation wasn't clear on this, I will need to test it myself).