Sorry for the late reply.
No, you're not doing anything wrong. It looks like we've got a bug in our handling of relational properties. In this case, since we've seen the EntityKey for CoverageIntent before, it should be in the QueryCache and we should therefore look in the EntityCache for the entity, and not go to the database.
Thanks for pointing this out. I've opened a bug report for this issue.