So almost all so "gaming" routers are garbage. At very best they have preset preference for a very small number of game that they recognize. What you are paying extra for is that a dev at the router company loaded some preconfigured QoS rules so that you did not have to type them in. The rules actually pretty easy to do yourself but are also pretty worthless which I will explain below.
Before I get into the big messy discussion of QoS the best solution is to always buy enough bandwidth so all your applications can run at the same time. Can you just buy more internet bandwidth......
So this is long and complex.
You only need QoS if there needs to be a choice which data to send first. When there is enough bandwidth all data will be sent with little to no delay. You only need to mess with this if you are hitting 100% load...or more exactly if you are trying to exceed 100%. In this case something has to be discarded. It all depends on which traffic you find more important, some people would say netflix was more important than their kid who doesn't pay the bills game traffic. This is not a technical issue it is more a family issue as to what traffic is more important. Another reason a ISP does not want to even think to mess with this issue.
The key issue the ISP will not do any kind of QoS with your data. You can control outbound...ie upload.. data priority but you have no control over what the ISP sends. There is no solution if the ISP were to send a packet for netflix and discard a packet for a game. By the time your router figures this out there is nothing it can really do.
So almost all so called QoS solutions that try to affect download traffic attempt to trick the application on the end device into requesting less traffic. This is a very complex topic related to a topic call window size. What the router does is even though the ISP sends the traffic when the router receives it if the traffic is to be limited it will pretend it never got it and discard it. The hope is that this causes enough data loss for the end device request traffic a slower rate. Again very much oversimplification. This should in theory then leave enough bandwidth for the machine that needs the traffic.
So in some routers you can more or less just say xxxx device get a minimum bandwidth. This will limit all other device. It kinda works and kinda doesn't.
There is a much more advanced form of QoS that attempt to treat all traffic as equal rather than having to put rules in for each device or game. This mostly helps game traffic which is why you see it on forums like this. It doesn't help other traffic as much if you would need to prioritize it. It also has lots of trouble with the newer download methods used by steam and other gaming sites that running multistream downloads similar to how torrent works.
So if you still really want to do this I would look for a asus router that can run the merlin firmware. It has a number of option but if you look for the terms bufferbloat and maybe "cake" you will find discussion on setting stuff up like this.
BUT this really only works well on smaller connections, say under 100mbps. This is also tends to be the ones that actually need to have a QoS solution. The problem is any form of QoS put a huge load on the router cpu and they are tiny. If you had say 1gbit internet you would be capped by these type of policies to under 100mbps in many cases.
Then again if you have a big internet connection more than 100mbps you have very strange traffic. The only thing that can realistically overload that is large downloads. You are going to be better off trying to get everyone who shares the connection to use the options in most downloaders to limit how much bandwidth they request rather than trying to enforce something with some router. This again gets into non technical issues, if you have some teen who just can't resist using torrent to download questionable stuff 24x7 that is a different issue. Note even very fancy qos can't stop torrent it is designed to bypass restrictions from when ISP tried to use QoS to limit torrents.