Meshtastic is also making improvements based on things seen in meshcore. For example, in the 2.6 firmware, next hop routing was introduced for direct messaging that makes the direct messaging paths more efficient and in the latest 2.7 series firmware, it also disables telemetry by default and makes it only upon request to remove some of the airtime used by that. Personally, I have flashed my node over to meshcore as well, but it's at least a good thing that meshtastic is taking some of the good things from meshcore and implementing them as well.
Do be aware, though, that 64-hop limit is only with 1-byte paths. If you move that up to 2-byte paths, that drops from 64 to 32. And if you move that up to 3-byte paths, then it drops from 32 to 16. The benefit with the multi-byte paths is that you have less collisions and therefore your path information is going to be much more accurate.
