Golly felt clunkier using RuleTable, but after your reading your message, I increased the memory allocated, changed the step size, and everything improved.
A warning to anyone else reading this: one problem with rule tables like mine and Tropylium's is that they don't know whether the generation is odd or even, so it is possible for cells to be out of synch with each other. This could be seen as a feature, but it is a bug for emulating Golly's treatment of B0 rules. Using random fill is an easy way to accidentally end up with out-of-synch cells, and it led me to throw out a proposed spaceship-to-glider converter.
I think the answer is to create a python transition function which can use golly.getgen(),
and then use make-ruletree.py instead of using a rule table. (More things to learn how to do!)