I am not sure if you are being sarcastic, but almost two years turnaround time, I wouldn’t call impressive 
I'd say Anav is still being mild ... 
More impressed that chaos had time to respond! I imagine changing the config of probably around 2000 deployed routers to upgrade to the new functionality cannot be a trivial exercise.
It certainly indicates zerotrust cloudflare as an options package and interface lists in routing rules are dead ducks, but gives me hope that other suggestions may still be in the pipeline maze of updates. ,-)
To be fair, this is a long-time feature of wireguard. Absolutely glad Mikrotik has added it!
I’ll definitely try it out.
@Chaos/Lurker, Can you explain how I can test this and your config......
Lets say I have R1 hosting wireguard, connected to it is another router R2, I setup wireguard normally, and also a road warrior. Both routers have 192.168.5.0/24. Thus far we have only been concerned with R1 subnet 192.168.1.0/24 and R2 subnet 192.168.2.0/24.
However new requirement comes in, the OP wants 192.68.5.0/24 on R2 to be accessible to users on R1 from 192.168.1.0 and as well, wants 192.168.5.0/24 on R1 to be accessible to users on R2.
Do I need to remove the first wireguard interface and start from scratch, or do I need to modify the current one, or do I need simply to create a second wireguard interface.
Besides the wireguard interface creation, what other rules or config spots are affected.