Personally, I'm also kind of on @lokki's camp in using axoloti mostly without a PC, and to be honest, a perfect undo/redo is at the bottom of my list of issues with Axoloti.
That being said, looking at the current code that's generated, there doesn't seem much oportunity for avoiding function calls usually, so I wonder if this changes would have any practical impact over performance. Also, if objects are pre-compiled, I imagine that there would be some oportunity to do some function inlinining inside them, wouldn't it? specially if code sharing is implemented. So am I correct in thinking that most of the extra function calls would come from small objecs with small methods being connected to other objects? If that's so, I don't know, it doesn't seem like too much of a problem to me.
I wonder, if it results on being a significant problem, would it be too hard to add some kind of "freeze switch" to subpatches, so that they are precompiled as a whole, trading the ability to modify their insides for performance?
Even though I also don't really personally care about the issues this seems to solve, I applaud the decision to do it. I'm familiar with starting a big project, realizing a lot of time later that some desired features need it to have a significantly differente paradigm, but leaving those changes for later, because it's too much of a hassle. Then, the more time that passes, the harder it seems to make those changes, and any other development is affected by the ghost of those changes, because you know, once you change the paradigm, you'll have to redo a lot of that develpment. So I'm very happy with movement; any sign of life is better than a stale codebase.