This +1. I've been burned before when using ORMs which translate simple-looking queries to terribly inneficient SQL statements underwater.
N+1 looks like an issue with aggregation after a parallel run, something I've encountered with celery tasks before.
Most ORMs do lazy loading by default, but also have a way of doing eager loading — either requiring the nested object to always be loaded as well, or dropping down to some pseudo-sql.
In c#/EFCore, I always prefer to avoid lazy loading and just write LINQ, and just use the ORM to map the resultset back to objects