I think the discussion in the comments to the other answer deserve their own answer:
First, while you can list the routing table with
ip route or
route -n and work out yourself what's likely going to happen, it's easier to just ask the kernel with
ip route get a.b.c.d to go through the routing tables (yes, there's more tables in a modern Linux system, and
route -n only shows the main table) and tell you the outcome.
Second, a rule of thumb for designing a network is "each host only gets a single network interface into each subnet it is connected to". Here VMs, network namespaces etc. count as additional "hosts", even if they run on the same hardware.
A corollary is "no, you don't assign multiple IPv4 addresses to the same network interface" (unless you know what you are doing, but then you do that at your own peril).
The reason is that nothing is won by making a subnet accessible through different network interfaces: It will go into the same subnet one way or the other.
If you violate these rules, as you did above, where you apparently have two WLANs connected to the same subnet:
10.0.0.0/24 dev wlp3s0 proto kernel scope link src 10.0.0.120
10.0.0.0/24 dev wlx00e04c221395 proto kernel scope link src 10.0.0.143
then what happens is not defined. As you can see, the linux kernel happily picks one of the network interfaces at random for destinations
So either these are really connecting to two different WLANs. In that case, change the IP range of one of the WLANs, e.g. to 10.0.1.0/24. Or, they are the same WLAN, and in that case having two WLAN adapters makes no sense.
It's similar with the default rule. You should only have a single default rule; having multiple rules means the behaviour is undefined, and a rule gets picked at random. This means that packets in one connection are randomly sent with different parameters (e.g. source addresses), and the host on the other hand will only recognize one set of parmameters (the one the connection was opened with), will drop the other packets, and will consider the missing packets as lost packets. That's because the standard internet protocols are "single homed". There are multi-homed protocols (like SCTP or multi-home TCP extensions), but they are currently not used widely enough to be useful.
So no, you can't use two ISPs to connect to the internet and make "the internet faster" (unless you have some hard way of deciding which connection to use, e.g. by destination address). That's a FAQ that gets asked every week or so.
I hope that answers all (or at least most of) the questions you didn't ask in your original question.