All that ip route list does is list all of your routes currently in place in the network routing table. The significance of the order of info in the output is less important than the metric values and route table structure for more complicated configurations. Also, and more importantly, basic understanding of how network routes work is key to interpret the output so you understand what each line refers to.
As such, the significance of device order in the output is nearly zero. More important is the Metric value on the default routes and other routes on a per-device level. So ignore 'device order' entirely, and read the routes as you would a list of directions.
So let's first look at the non-default routes, and interpret them as such (based on the data):
Traffic to 10.0.0.0/24 via device wlan0 are on-link and will be sent via this device with a source IP address of 10.0.0.129.
Traffic to 10.0.0.0/24 via device Ethernet are on-link and will be sent via this device with a source IP address of 10.0.0.120.
Similarly, now that we know the on-link routes are in place, we refer to the following interpretation of your default routes:
The default route for all traffic destinations other than on-link routes is via the gateway 10.0.0.1 via device Ethernet, which has a distance/metric value of 1000. This link has the lower distance/metric value and will be used first.
The default route for all traffic destinations other than on-link routes is via the gateway 10.0.0.1 via device wlan0, which has a distance/metric value of 2000. If the link/route to Gateway is unavailable on Ethernet, then wlan0 link will be used instead.
This is how you interpret the data, start from the non-default routes and then compare default routes and the metric values.
(Note I shortened your enp... device to just Ethernet for this discussion and ease of typing)
