complex Eloquent queries causing N+1, need optimization strategies

we've been working on a Laravel Quick Fix & Consultation project for a client, dealing with a particularly complex legacy application. the main bottleneck right now is around data retrieval from several interconnected models.

• The Core Issue: we have specific reports that require data from deeply nested relationships, often involving polymorphic relations and dynamic conditions. this leads to incredibly slow load times due to inefficient Eloquent queries, despite using eager loading where straightforward.
• Attempts Made: we've experimented with various combinations of with(), load(), and even custom scopes. for some parts, we've resorted to DB::raw() or join clauses, but this breaks the Eloquent paradigm and becomes a maintenance nightmare, especially with the dynamic filtering requirements.
• Specific Pain Point: the N+1 problem persists in scenarios where conditional relationships are involved, or when aggregating data across multiple, optional related tables. for example, retrieving a list of "items" where each item can have one of several "detail types" and then needing to filter based on properties within those specific detail types.
• Seeking Advice On: advanced patterns or techniques for optimizing such intricate and dynamic Eloquent queries in Laravel. are there better ways to structure these queries, perhaps using view models, or specific caching strategies that don't just cache the final result but optimize the query execution itself for complex joins?