managed to help out a bit on the freezing, even though it is a very crude hack,
...
to 2000 or something.. seems to be able to move around a bit now at least without locking up completly..
The reason that you're freezing up is that thread.sleep just murders the game UI instead of what it used to do, murder HB and any bot commands. This change is also why object gatherer had to be changed to a bot, and why a ton of useful plugins are now integrated into bots instead. Eg. WoD timber gathering.
If you have framelock enabled, sleep causes all of the regular processes to stop working, including responding to the framelock, which causes the game UI to freeze up. Its not restricted to framelock though, because the bots are now operating in the same thread as plugins and combat routines.
Prior to the change, plugins used to operate in a separate space to the bot and subsystems for HB to operate. This is still the case, but it prevented plugins from being able to access framelock events as well, eg for quest behaviors. By using the same thread as the bots and routines, it means that all plugins now have to play nice with each other and not steal time or try to override each others actions.
What you have to do is stop pokeh from always retrying, because when the framelock is active, each pulse loop runs for 50ms (20fps) , or up to 32ms (~30fps) to access the game. If a command takes too long to execute, it doesn't just delay honorbuddy, it delays the game as well now. And the plugins have to share the same thread as combat routines, movement, navigation, bots, quest behaviors, etc.
This also means that the old strategy of using thread.sleep to override bot movement won't work. We would need a way to tell the bot to pause, and there are no HB API's or functions to achieve that. Hooks could be used, but there's another series of problems with using hooks. Although it could be made to work, it's not supported or documented, and it's not a realistic answer because the bot author also has to support using them, which has not happened.
Anyway
You can hack this by changing the sleep lines to wait timers, or timer functions, (one is built in, one comes from the system timer) and putting the new timer into the if statements, then resetting/starting the timer when you reach a point where you need to wait.
If this is too confusing, just have a look at examples from the quest behaviors, or other plugins that require movement.
It won't work to replace the old behavior, but it won't lock up the game anymore. Using smaller time increments will be more difficult, especially because plugin triggered movement is now at war with the bot triggered navigation and movement in the same process thread, with no ability to share or set hierarchy or queue commands, etc.
In short, the plugin is fantastic, but it is being outmoded because of the lack of working hooks in the builtin bots like GB2 to override movement for a few minutes. Until the hook works, or GB2 is modified to allow pokeh to trigger, it's difficult to imagine a workaround.