When to use custom resolvers?

[ricardo-valero]

My HotChocolate server is using EF Core 6 with projections.
Will using custom resolvers solve issues like:
warn: Microsoft.EntityFrameworkCore.Query[20504] Compiling a query which loads related collections for more than one collection navigation, either via 'Include' or through projection, but no 'QuerySplittingBehavior' has been configured. By default, Entity Framework will use 'QuerySplittingBehavior.SingleQuery', which can potentially result in slow query performance. See https://go.microsoft.com/fwlink/?linkid=2134277 for more information. To identify the query that's triggering this warning call 'ConfigureWarnings(w => w.Throw(RelationalEventId.MultipleCollectionIncludeWarning))'.
Don't know much about query splitting but here's the issue with projections:
dotnet/efcore#21234
Any recommendations? If I were to write my own resolvers will there be any significant performance improvement?