Yes, with 1.35 it is making it a static IP, but that does nothing about the routing
if you set it to 1.35/32, then you won't be able to connect to anything else on the network through that port (as there are no other devices in a "range" of 32).
The subnet tells it what IP's / Devices are within the "local" network, so it can just "ask around" on the network, and for anything outside of that range, it knows that it isn't local and it needs to ask the "default gateway" device, as that device should know where to get to that other device.
So in your example you have 3 IP's all in the same "local" network, the network 192.168.1.X
Now a packet needs to go to 192.168.1.222 for example, how would the PC know which of the 3 devices to send that traffic out from? Since they are all local, they could go out from each of the 3 ports at random, although usually, because that port has the default gateway and lowest IP, it will probably pick the vmbr0 port.
There are ways to tell it "for traffic to IP A, always use port/IP B", but just using separate ranges is more stable, more easily set up, and more frequently seen as as such understood.
If you set your IPs to
vmbr0 192.168.1.25/24
bond 10.0.0.25/24
vmbr1 10.0.1.25/24
on server 1 and
vmbr0 192.168.1.27/24
bond 10.0.0.27/24
vmbr1 10.0.1.27/24
on server 2
If you say "Server 1, send this traffic to 10.0.0.27", the Server will check if it has an IP in the range that is requested and finds the 10.0.0.25 on bond, so it's uses the bond and neither of the other 2.
Similarly, if you say "Server 1, send this traffic to 10.0.1.27" it will find 10.0.1.25 and use vmbr1, and if you want to go to 8.8.8.8, it will not find that IP on any of it's devices, so it goes and ask it's default gateway, which it knows to find on ip 192.168.1.1, which it then can find from 192.168.1.25
