As I understand it, when the Rocket re-boots in Accelerator mode after enslaving the host CPU as a mere I/O CoPro, it runs the NuBus via AppleTalk over NuBus and does Block Transfer Mode with all Compatible Cards.

As I understood it back in the day, the Rocket acted independently of the host CPU, interpreting and issuing the interrupts for the NuBus Slots over the NuBus.

In this way, the Saturn V used a "lowly" SE/30 to copy its ROM to a multitude of Rockets set up in a huge expansion chassis without any regard for the SE/30 as anything but a simple controller terminal . . .

. . . amd the SE/30's not even NuBus Compatible other than via the Two Slot ExPanse Chassis, AFAIK! }