Routes belong to IP interfaces, not bridge ports. Your bridge ports shouldn't contain literally anything. All routes are associated with interfaces that have IP addresses.
Consider if you had this:
auto eno1
iface eno1 inet static
address 10.83.86.10/24
up ip route add 10.83.86.11/32 dev eno1
down ip route del 10.83.86.11/32
then it becomes this:
iface eno1 inet manual
auto vmbr1
iface vmbr1 inet static
address 10.83.86.10/24
up ip route add 10.83.86.11/32 dev vmbr1
down ip route del 10.83.86.11/32
bridge-ports eno1
bridge-stp off
bridge-fd 0
Notice how all IP-related stuff just simply moved from physical NIC into bridge. The NIC becomes L2-only interface, think of it as a switch port. Switches don't have IP addresses on each interface, neither bridged interfaces should.
You can bridge several physical NICs as you did by specifying them all in bridge-ports. None of the ports will have an IP configuration. Only the bridge can have it.
I can't understand what you are going to achieve by having each interface individual /32 address and individual route. I don't know why you want that, but this network setup looks rather strange.
Yet if you want to keep the network (layer 3) structure as you have in your question, you need to create a dedicated bridge for each IP address and put respective VM into that bridge.
If this all is just for host-to-VM communication, you don't need to bring any physical NIC into those bridges. Leave vmbrX without any bridge ports, but configure an IP addresses. You will be able to put VMs into that "empty" bridge and they will communicate between each other and the host. The physical NICs only need to be part of the bridge if you need to connect this virtual network segment with physical network on layer 2 (e.g. Ethernet).
