I never really played with it there, but AFAIK Linux has this configurable (see “ip rule”) and default is what RouterOS had previously. It’s not necessarily the only right choice, it can be what RouterOS has now. The bad thing is changing something like this without any warning whatsoever. I’m pretty sure that many people with load balancing previously marked routing without excluding router as destination, something like:
/ip route
add dst-address=0.0.0.0/0 gateway=xx routing-table=wan1
add dst-address=0.0.0.0/0 gateway=xx routing-table=wan2
/ip firewall mangle
add chain=prerouting in-interface=LAN connection-state=new per-connection-classifier=something/0 action=mark-connection new-connection-mark=wan1
add chain=prerouting in-interface=LAN connection-state=new per-connection-classifier=something/1 action=mark-connection new-connection-mark=wan2
add chain=prerouting in-interface=LAN connection-mark=wan1 action=mark-routing new-routing-mark=wan1
add chain=prerouting in-interface=LAN connection-mark=wan2 action=mark-routing new-routing-mark=wan2
And why not, it always worked. But now if they upgrade, they suddenly won’t be able to access router. Most will probably have enabled access using MAC address, but it will still cause a lot of confusion. And again, the main problem, there was no warning.