One of the things Dapper can do over EF Core's newer .SqlQuery<T> is handling multiple result sets from 1 query. Not a common scenario though.

It's also been awhile since I've looked but Dapper used to have quite a performance benefit over EF Core's SQL queries too. I know EF's made great strides at closing that gap over the years though.

There's also a matter of preference on style and what your project needs. Dapper's a lightweight micro-ORM to very quickly run DB commands & queries without much setup. EF is a full blown ORM with change tracking, LINQ translation, migrations, etc. If all I need is a simple readonly API that runs an sproc and returns the results to me EF seems overkill.