My personal take: Don't put it all in the same box.

Just have a api/v1/rest/ base path for modular well defined resources that can be used across your application, without breaking changes, or even shared to third parties.

Then have a api/v1/features for coupled endpoints that return non standard objects, and with a more flexible lifecycle.

Chances are you're better off having both instead of trying to cram all the use cases into one approach