Nothing will stop you from passing in a Func<T,bool> type where you should be using an expression, but if you pass it to a Where on an EF context it will be run on the client instead of being converted to sql.
There is an entire API for building up dynamic expression trees and compiling them at runtime.
...and zero for the inverse, which is why Expression Trees are generated by the C# compiler at compile time, not decompiled at runtime.
You are right (as far as built in support goes), but it actually could be a fun project to take IL and build up C# expression trees from it. Especially given there are plenty of IL to C# de-compilation libraries out there.
In EF Core 3.x it'll now throw an exception at runtime.