Probably more detailed answer than this needs, but:
Although it’s much easier if you do offsets while you’re in Fusion 360 or some other high end CAM program, wear offsets can be done on some controllers. Theoretically, Motion could do all the computational heavy lifting to do this, even if GRBL can’t natively handle it.
However that’s not happening anytime soon, if ever for us. You generally need to have a database of tools used on the machine, and wear offsets applied to each. But as soon as you take an endmill out of the spindle, the offset is going to be different because the runout on an ER collet is going to change by a couple microns every time you put it back in the machine.
Wear offsets are only useful on machines with an automatic tool changer, where you need a systematic offset applied for subsequent jobs. If you have to go plug in a different number to make a one-off tweak to a toolpath, you might as well plug that number into Fusion and export a new toolpath. Of if you have a tool that isn’t up to spec, better to define a custom tool in your tool library.
While I get what you’re saying it would be a nice feature for those who use multiple computers. My workstation with the pro version is in my house while my machine controller “Surface tablet” is on my machine. Running back and forth modifying and updating the code kinda sucks. A wear offset would only really be of value if you could just re-start a program from a particular tool and override the touch probe value.
Restarting the program from an arbitrary point is on the roadmap, no firm ETA on it though.
More data in readouts is also possible, but likely not going to be a point update. Probably something to be weighed when more significant changes to the code happen. (I’m not the programmer, just extrapolating to the best of my knowledge.)
I can tell they have cool things in the works. The beta verson of Carbide Motion has some 3D visualization features in testing. So hopefully we get something that shoes is next moves, etc.