Building Out a Constituent Hierarchy

We are looking to build out a fixed Constituent Hierarchy for reporting and querying purposes and am wondering if anyone else has done this? I know that you can configure the hierarchy under constituencies, however, this is not fixed and can be changed by anyone who has access to it, which would effect the accuracy of reporting. This is also not visible to all users, as those without the appropriate security settings are restricted from accessing the constituency configurations.

We are looking at using the Constituency Stored Values to work around the issue of a static versus fixed constituency by adding rankings 1-20, each tied to a constituency that can be used in querying and in reporting.

Our third option is to build out a new data table that can be accessed in the query tool and pulled from for reporting.

Any help would be appreciated! Thanks.