When you have a network like yours, 192.168.0.0/24 (/24 = subnet mask 255.255.255.0), then you have a broadcast IP address for that network, which is the last IP address in range, ie. 192.168.0.255
If a device wants to send a message to all devices, then it sends the message to that broadcast address and the network gear will make sure that all devices in the subnet receives the message.
If you have a network, like 192.168.10.0/24, then that network will not receive the broadcast from the 192.168.0.0/24 subnet.
If the broadcast should be received at the devices on 192.168.10.0/24 subnet, then the broadcast address 192.168.10.255 should be used.
Broadcast addresses are as standard not routed, because there are a lot of broadcast traffic, which does nothing other than public information to other devices on the same network, so routing it would often mean a lot of unnecessary noise in the form of published information that are useless to other networks.
Your Windows machine might publish that it is on the network and that it might have a shared folder available or a printer connected that can be used over the network. This is an information you would probably want to keep on that specific subnet.
Remember that the 192.168.0.0/24 and 192.168.10.0/24 are just 2 subnets here. There will probably be at least one more and that is the subnet of your internet connection, which you also certainly do not want to publish your information about your Windows machine on.
You can make published information move from one subnet to another subnet, but that requires routing and this is where my router comment comes in, but it can be a big mess to handle broadcasts over different subnets and it requires a router with options for advanced routing.
Your idea of having HA on multiple subnets is not something HA is built for.
HA can not just run a single instance of each of the many discovery services and then connect those services to the different network, because most discovery services are autonomous in selecting a master accountant for the list of services and when that master accountant device gets shutdown, then another will be selected.
If HA gets selected, then the information from the different subnets would mixed together and you will have polluted lists from then on.
A router will run a separate instance of the discovery services for each subnet, but this is not something HA is built for and it is a complex error-prone undertaking to make it happen.
One error in these discovery services and you might have to shutdown all devices in the network to make sure that no master accountant holds a list with the error due to the autonomous nature of those services.
I would say as Tinkerer, use a bigger subnet instead.
A /24 subnet will give you 256 IP addresses and 254 are usable for hosts.
A /23 will double that to 512 IP addresses and 510 of these are usable for hosts.
Using 192.168.0.0/23 will give add 192.168.0.0/24 and 192.168.1.0/24 together in the same subnet and broadcast domain.
A /22 will double the /23 network and give you 1024 IP addresses and 1022 of these are usable for hosts.
Using 192.168.0.0/22 will give add 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24 and 192.168.3.0/24 in the same subnet and broadcast domain.
The 2 IP addresses in each subnet that is not available to hosts are the first one, like 192.168.0.0 in a /22 network, which is the network IP address and the last one, like 192.168.3.255 in a /22, which is the aforementioned broadcast address. In a 192.168.0.0/22 subnet the IP addresses 192.168.1.0, 192.168.2.0, 192.168.3.0, 192.168.0.255, 192.168.1.255 and 192.168.2.255 will be available to hosts, because they are not used for network and broadcast IP addresses here. Only the first and the last one of the entire subnet is reserved for this.
