Slow is relative. Zorro3 speeds are slow compared to what a gfx card can move around.
Relative is not the problem. If your PCI gfx card delays your PCI read just a few times, you are lost as the Buster will timeout the Zorro III cycle, leading to a bus error.
As you want to go to more memory I guess we are talking about modern PCI gfx cards and not the 4MB S3 Virge models.
Most PCI gfx cards nowadays are using PCI-AGP bridges, and so the problem gets worse. Those integrated bridges will add more delays, and the problem of write / read combining.
The bridge will follow certain rules when different read / write operations are pending, and this may lead to bad situations in real life (like: several writes are pending inside the bridge, followed by a read, so all writes will have to be completed before the read is completing -> long delayed read).
Do the buster problems occur with a Revision 11 buster?
The timeout is not a "problem". It's intended to break deadlocks when a Zorro III access fails.
Or do you mean the other Buster "features"? Which one, as there are quite a few of them, and they are available in different tastes in all Buster revisions :-(
Michael