QoS should let you set up priority queue handling and control bandwidth for links that have traffic contention. If you're running servers or P2P then you'll certainly get contention on your relatively slower upstream link.
From the Billion manual, looks like all you can do is allocate bandwidth for a fixed or minimum required value.
For Counterstrike, the game traffic is a maximum of about 30 kb/s. I'd allow double this so would put an entry in for LAN to WAN, and a percentage to give you 60-70 kb/s, local application port will be 27005 if you're using the default client port. The rest depends on what other traffic you have, like voice over IP would require 80 kb/s if using the G711 codec. I would also reserve about 5kb/s for DNS (remote UDP 53) and NTP (remote UDP 123) if you use it.
For WAN to LAN traffic, there's very little you can do since the traffic has already arrived. The best that can be done is to throttle any traffic that swamps your downstream during transfers. The theory is that this will leave enough bandwidth for other traffic, but tests I've made with my kit is that you need to throttle to at least half the available bandwidth for this to make a difference. So you have to make the choice of fastest downloads verses better gaming, though you could have this on a time schedule.