So your blueprint is referencing a script from C++; you’re going to have to replace every single instance of iTween with the new blueprint-only calls. Then compile and save, it should be fine as long as there are no traces of C++ iTween calls whatsoever.
Hot reload is going to take ages the first time or if you edit any iTween source files, but after it’s been compiled it shouldn’t take long if never changed - at least that’s the case for me. I know it’s super unhelpful to say “hey, works on my system” but that’s pretty much the size of it. I think your best bet is to remove the plugin and go back to the C++ version. Give the engine a little time to acclimate, hot reload times shouldn’t be a problem for long. If they continue to be, if you’re comfortable with it I’m glad to take a look at your project and try to figure out the stopgap.