Realize that the liquiduct limitation is per input. Just like you should have multiple connections for steam on a boiler, but it all travels through a single pipe.
i.e.: Connect the liquiduct to more than one face of the bioreactor.
Does not work. A bioreactor will only output to a single pipe or liquid inventory.
Now, FWIW, it's going to be very hard to automate a 9 item reaction without putting in one set of items, turning it on then off, putting in another set, etc etc. There is no logic in the game whatsoever that can investigate the "production bar", all logic available is only going to examine the 9 slot pre-production inventory. An emerald pipe or router on blocking mode can simply load one of each and block until it receives proper input, but are both so slow even with guaranteed inputs as to mean you'll have to turn the reactor off more than its on.
What I eventually came up with was a turtle (it doesn't need to move, but computers, even with peripherals don't have enough inventory space) that waited until it had a stack of each then turned it off, dumped the items (the full stack, minus one to keep for comparisons) all at once, and turned it back on. This also lets me configure a timeout or redstone trigger to drop down to an 8 or 7 or 6, etc items reaction. The redstone trigger could be used on a liquid level sensor on a xytank - if the fuel level dropped, go into panic mode and generate some even at reduced efficiency.
Again logistics pipes makes this exceedingly easy as do managers and someone has suggested AE. It also isn't terrible difficult to setup a system to check if one of the items being supplied is missing and when true it sends a redstone signal to the bioreactor shutting it down.
One it's can't pull and it's can actually teleport a bucket per tick but it's can't pump liquid out.
It cannot move a bucket per tick from what I just tested. It moves the liquid no faster than liquiducts; as it should be.