"@sns Still, one can benefit from a 'clean' home network."
This needs to be clearly defined. Are we talking about a clean network, or clean components from an audiophile stance? Sadly, us audio guys try to treat networking like our stereo systems. They are not even close to being the same.
Have had several people say they have a "clean" network for streaming. Sadly, you do not. You have a network segment, separate from your home network. This does not give you any benefits to steaming. If you want a "clean" network, it takes a ton of work to keep all traffic off the network except for streaming traffic. In networking we call this "air-gaped" You have a network bridge, and firewall, sometimes a dedicated point to point VPN, or packet encapsulations. Then you do some port forwarding, QoS, segmentation, setup the firewall to only allow the ports needed on the streamer, along with closing off all other traffic, etc...
I can put a packet sniffer on any of these clean networks, and in about 10 sec of sampling tell you all the "noise" on your network. This all means nothing. If you have a 100g network, a few thousand bits of network traffic will have 0 affect on your streaming.
My point is, having a streaming network is mostly pointless unless your main subnet is full, and/or is having any kind of packet collision issues.
Now if we are talking about WiFi, that is an entirely different issue. No enterprise gear will have networking and WiFi in the same package. Wifi is also "air-gaped" while being radio, it will not contain anything ridding on the original packet from the source to the destination.
FWIW, I used to work for the company that supplies the full racks to AWS that AWS runs on. Was an engineer then architect, dealing with server farms over a thousand racks. Being on-call to AWS, and working 80hs a week was not for me.