Yes, good thoughts.

But - sorry there is a but - too often, development and delivery practices are left out of retro discussions, because the Scrum Master does not understand the technical side of things, so developers hold back on those issues during the retro.

DevOps metrics - rather than OKRs - should be the primary focus of developers. That is, unless you are building a single team product. But if you are working on a product that is supported by tens of teams, then your team has little control over business value. What you DO have control over is how you build, test, and deliver. Those issues should be primary topics during a retro.