The problem is generalizing the solution. It's fairly straightforward in our implementation in HH because we're architecting in a very specific manner with how we are structuring our memory, our data structures, and where our code is going and being accessed. Taking that and putting it in arbitrary code for hotloading is... problematic. Like anything in computing, it can be done, but at what cost?
With C++ specifically, and things like classes or whatnot it requires a lot knowledge of the underpinnings of those implementations. vtables, inheritance profiles, etc, etc, etc. It's a lot simpler our way because we're not messing with those abstractions (and for good reason, they don't give us anything). This couldn't be done randomly for any application, so it's probably not worth the effort to break the problem out into a solution anyone and their brother could use.