Difficulties with ethernet interfaces on map2nD with 6.35.4

I’m using a map2nD router with firmware version 6.35.4, and I’m having issues with the naming of ethernet interfaces whilst having a USB-to-LAN adaptor plugged into the micro USB port.
The issue I’m having is that, on reset of the AP, the USB-to-LAN adaptor does not always appear as ether3 in the AP config, sometimes appearing as ether1. This is an issue as, not only do the config names no longer match the names printed on the device but I am trying to programmatically make changes to the config using the API, and this is very difficult if I do not know which interface is which.
Is this a known issue with this version of the firmware? I was not having this issue with version 6.30.4 on the map2n. Is there any way I can identify which interface matches which physical port from the API?

So my solution to this problem is to, instead of relying on interface names, is to look at the mac addresses of the interfaces and see which one doesn’t start with the routerboard manufacturer ID. From there, I’ll have to make some educated guesses on which ones are eth1 and eth2, or maybe assume that they’ll come up in order (though that goes against this issue in the first place).