1. Well, you can do this already if you know how to open the console with F1 and type in 'net.connect <ip address:port>. I think part of the problem with the server browser is that as soon as you hit the 'play' button it automatically starts querying every server in the database and doesn't stop until it is complete. I play on an Official server, so when I click on the 'Official' button and enter my server, the game is really laggy for about 20 seconds, because I believe the server browser continues to query every server in the database in the background even after I have entered the game. I now open the console command and manually connect to bypass this lag.
2. This won't work. If the DDoSers have any brain, they can easily filter out the servers that return 0-20 players or return 999 pings and focus on the more populated ones with realistic ping times.
3. Still won't work. Even if you change all the I.P. addresses and ports, how would you distribute that list to people who want to connect via the console? If you make the list public on a web site or blog, then the DDoSers will still find the servers. You can't win.
Here's what will happen, in my opinion:
1) DDoSers get bored. (not likely).
2) Gary's host fixes their security holes. (quick fix)
3) Gary finds a new host. (best option in the long run)
For this attack:
Actually only the library needs patching. That it closes the open connection if there is no data or incorrect data is send.