> Yeah, but with lightning you really need enough value along the network path(s) to execute a transaction, possibly causing a similar thing as this to happen.

It's atomic, it either completes 100% or it fails, there's no partial state where the money gets stuck in one of the middle-nodes.