svnadmin dump/load restore limits for hooks and config verification

Restoring a Subversion repository from an svnadmin dump stream is intended to recover versioned history into a new repository.

The documented behavior is that dump/load transfers versioned data only and does not include repository configuration such as hooks, conf files, or authz. svnadmin verify checks internal database consistency after load, but its scope relative to content equivalence with the source is unclear.

For a restoration that must preserve both history and operational configuration, the boundary between what dump/load supports and what must be handled separately is not fully defined.

Does svnadmin verify provide any assurance that restored revision content matches the pre-backup repository? What is the supported behavior for repository UUID when loading into a fresh repository? Are hooks, svnserve.conf and authz considered out of scope for dump/load by design?