USB 2.0 hubs have a dirty little secret. Most of them use a chipset based on a single translation design, as these chipsets are cheaper. The translation handler affects how the USB hub deals with USB 1.x devices that are connected to it. And since the Virus is a USB 1.1 device, this is important.
With a single translation based chipset, all USB 1.x devices on the hub share a single translation channel. Thus, if you also have things like a keyboard or mouse connected to the hub (which are almost always still USB 1.x devices as well), they will share a single 12mbit USB 1.x channel back to the host machine with your Virus. Many music controllers (e.g., Akai MPD series, etc.) are also USB 1.x devices. Sharing a single USB 1.x channel can result in bandwidth issues, sync issues, etc. You want to avoid single translation chipsets.
Multi translation chipset designs give each USB 1.x device its own 1.x<->2 translation channel. Thus, each device gets its own dedicated 12mbit USB 1.x channel to play with. You no longer have to worry about conflict between devices, and USB behavior for things that are timing and/or bandwidth sensitive will be MUCH more stable.
But as I said, most USB 2 hubs use a single transaction chipset to save on cost. And nobody publishes this in their tech specs (even the folks making hubs based on a multi transaction chipset it seems). Without calling and consulting with tech support, you usually have no way to know. That said, one hub that is known to have a multi transaction chipset and which I personally own 4 or 5 of and have had no issues with (not used with the Virus, but with other audio interfaces) is the Belkin F5U237v1 7-port USB2 hub. I'm not sure if this is the same as the Apple hub you mentioned or not (did not follow your link, sorry). You mention power problems, which I've never had, as I always use the included power supply to drive the hub.