VBA 20's development introduced some new glitches:
Bad frame advancing on GB games
Another frame advance issue
Frame count updating
SGB Border graphical glitch
Inability to distinguish emulator versions in header data
Additionally, it has different timing, which we are being told is more correct. Not to discredit the developers, but SNES9x 1.51's new timing is (according to my admittedly un-bulletproof tests) actually less accurate. How do we know this method for VBA is more accurate?
VBA 20
seemed to be put together quickly without testing and such, and was just accepted as the new one to use. Perhaps this wasn't the case. However, due to glitches like this, I don't feel like using the version, and that's why I've continued to use VBA 19 on my TASes.
My point is, these bugs should be worked out before VBA 20 is treated as the "official" version to submit movies with. Until then, leave it in beta for people to test until the kinks are worked out.