To be honest, I'm not sure right now if/how it can fit into our plans.
Of course right now we have a different architecture and tour format (MediaWiki instead of Drupal, JavaScript API-based tours instead of Selenium-based ones).
Also, we have some things that may or may not have equivalents in WalkHub/Selenium. For example, we can listen for a JavaScript hook/event fired by part of our codebase to know when the tour is ready to proceed. For example, the VisualEditor can tell us if the page is now save-able, so we know whether to point to the save button, regardless of how the page became save-able (typing, bolding some text with the toolbar, etc.).