Excavator pathfinding bug?

This excavator is trying to take a ridiculously long path to dig this tile even though it is directly next to the tile that needs digging when the save is loaded. @piggywhiskey [discord] says this is due to the excavator first picking a spot to mine (the gentle slope of the far side) and then choosing a path, but is this truly intended behavior? I find it extremely unintuitive, at the least. The map is "Conquer The Mountain in Style" on the hub.
Last image shows the path the excavator is taking to the target tile.

From what I can tell, the MiningJob.targetTileCostFunction is the cause. It takes in distance as the crow flies, not pathed distance. Which is normally good, but this unique situation with limited access is causing the problem.

As it's generally preferred to not move the excavator, maybe the minimum weighting could be increased to handle these edge cases
thicknessTilesF.Value.Min((Fix32) 2).Squared().ToFix32();

This pathfinding is still being extremely inefficient sometimes.
Devs, can we please have the option to tell our mining towers to have excavators only dig tiles starting from a certain direction?

I can't count how many excavators I've had get stuck because they dig from the wrong direction and cut off their access.

Maby just something in the pathfinding, so excavators only move as little as possible and will only dig a slope from the side that is the same height that the excavator is standing on.
That way it can never dig a slope from the far side and it cannot block its own exit