svnserve+SSH minimal footprint vs mod_dav_svn per-path authorization for constrained Subversion deployment

Design choice for a Subversion server under a resource-constrained host with a requirement for path-level access control.

svnserve with SSH provides a minimal footprint and no external web server, but documented behavior shows it lacks per-path authorization. mod_dav_svn via Apache provides fine-grained access control through standard Apache directives, at the cost of additional process resources.

The deployment constraint is low memory and CPU overhead while still satisfying per-path authorization. An additional uncertainty is the long-term support status of svnserve; community discussion notes no official deprecation roadmap as of early 2025.

Assuming Subversion 1.14+ and Apache 2.4+, which documented access model can satisfy per-path authorization without adding a full web server stack? Is there an official statement on continued maintenance of svnserve versus http/https-only workflows?