Based on the way things act, when there is lag, It seems to me that the way loading is handled triggers a database transaction when moving each item going from a BSB to a Crate, or your inventory.
If a loading interface was built that could make it so loading 300 dirt, from a BSB to a crate, would be a single transaction, instead of 300.
This same interface could also allow optimization of the task of pulling something like wemp out of a BSB, combining 64 into a single bundle and then loading it into a raft
The interface would need at least the following items.
Input source box - A BSB, FSB, or crate would be added here, with the same type of process used in the "Add to Crafting Window"
An output destination box - A crate, or raft would be added here
A toggle for auto compression (example: 64 wemp becoming one wemp bundle)
A box that defaults to max compression, but can have a number set to control how many of x, gets compressed into one.
I think this should still not automate things like pan filling, but would certainly ease the load on the client and server by allowing a single transaction to be processed instead of hundreds, or thousands when moving bulk products for sale/transport.