Fix direct execute() calls

This is a sweep of the codebase that checked calls to `execute()` with made directly on a class name.  Each instance was handled in one of a few ways depending on what I thought best matched the style of the containing module.

No good reason!

I was preserving existing behaviour while removing a misleadingly named variable, but you're right that the code is improved by adding a check instead.