I think there might still be an issue with Program Changes with vst3 but not with vst2. Below is an Overloud email response I received on 8-29-16 about this (email pasted below). I'm assuming the issue still persists but I haven't tested vst3 with newer versions since then. When new releases come out, I only install the vst2 dll. And I uncheck Preferences->"Hide Related VST2 Plugins" and "Replace if Possible on Project Load". This is what TH3 suggested I do and then program changes work for me. I don't think there is currently any other midi issues other than Program Changes. Oh, and I'm running the full version.
Email from TH3 8-29-16:
There is absolutely no difference in functionality between TH3 VST2 and VST3 (aside, of course, of this issue regarding MIDI which is obviously not intended).
The current state of TH3 VST3 as of version 3.2.2 is that it supports CCs and Note messages, but still not Program Changes.
It may sound funny somehow, but the VST3 specification does not include "out-of-the-box" support for Program Change messages, replaced by a much more convoluted abstraction (which no one really uses in its full capability).
The result is that the old "Program Change" functionality has to be "emulated" instead, in some way or another. At the moment we're deciding which way it is best to design this emulation.
The good news is that the VST2 is still fully functional with all its MIDI capability, so if you wish to update from the special 3.2.0 that we have sent, you can do so updating with the latest 3.2.2 and then remove the VST3 plug-in from your system (or choosing not to install it right from the installer).