Yes this is correct. On one rig I have 3 AFX3’s in an aggregate device along with a T3 interface. So I have 3 USB cables and one T3 cable connected. No analog or even aes/spdif cables are used. At one point (in transition) I had 4 additional AX2’s connected.
There are some caveats... the io naming makes the initial setup terribly confusing. You can achieve 2 stereo loops through each AFX3. So to the way io is partially hardcoded, you can’t get 3 or 4 loops (sounds like Cliff may address this in a future usb and version firmware).
Also, re-checking (and sometimes reordering) the devices in the aggregate is sometimes necessary depending on your computer and usb hub situation. This can happen if you use a laptop and unplug/plugin different devices (eg you plug-in to a dock or add a usb device or hub). If your setup is relatively static, you may not see this issue.
Make sure your usb hubs are properly powered. Sometimes you may have the correct total power to support the axe on a hub but do to the startup sequence, there can be a surge that forces a re-ordering of the usb device ids on the Mac. That will cause an id mismatch in the aggregate and lead to the rechecking issue mentioned above. If Cliff allows us to name the axe with a unique name, there will be a workaround for this on the Mac (using a script that watches for connections and the fixes the id issue based on the axe midi device name). I’ve demonstrated that this works but need the ability to uniquely name the axe.
I solved this by dedicating hubs and a computer to the rig and it hasn’t had any id issues since.
One last thing... you must have your clocks synced properly. I use my T3 as the main clock. The other interfaces must follow the main one and also be set to drift. I have additional interfaces connected for the T3 interface and once accidentally had one in the chain as the main clock with the T3 as secondary, but set as the main on in the aggregate. This worked most of the time. Once I fixed that, the clock has been rock solid. The ONLY times I have sync issues now is with individual AX3’s if I load a preset via AxeEdit. Occasionally the load process (I think) is too much and disturbs the sync on that one AX and I get garbles audio from it. To fix it, I just reload the preset.