Dapr Workflow number of hops compared to Azure Durable Functions out of process

From my understanding, when it comes to workflow persisting state and resuming, there would be no difference in the number of hops between Dapr Workflow and Azure Durable Functions since the persistence does not happen in my code but only when my code awaits and gets automatically persisted by the either Dapr Workflow runtime or the Azure Durable Functions Out of Process engine. Then the engine wakes up and calls my code. Am I missing something?

Was not sure where to ask so I asked on both
https://github.com/dapr/dapr/issues/7544