If you need .htaccess, you’re probably doing it wrong.
Technically, it makes sense. Though I don't think most customers would notice any major improvements doing that. And we don't provide user access to the servers NGINX config. So unless you build your own NGINX+PHP stack from source (for example, using a 'proxy port' app to serve your site directly), users here will not be able to implement such rules as substitute for .htaccess via Apache.
PS: This may be useful for those wanting to go that route - 'HOWTO run a private PHP-FPM stack on Nginx or Apache on Opalstack'
That kind of thing used to keep me awake at night.
In the days when accessing files made grinding noises come out of disk drives, the thought of making unnecessary file accesses was almost unbearable.
Nowadays when it's all solid state, I sleep much better.