Use configuration files to enable or disable the new dyncom interpreter.

I think you should revert the changes to this file and just leave it as `kFrameCycles = 268123480 / 60;` for both cores. I'd like to understand why decreasing kFrameCycles breaks the slower interpreter before we change this, and it seems hacky having two different code paths for the different CPU cores. FWIW, the original value works for both cores, it's just that homebrew skips frames with it with the faster interpreter.