Update:
We may have to re-think this approach, the last we tested on Honeysuckle bugfest even with a single UUID the inventory hierarchy API didnt give a response. Until we know t
1) That the Hierarchy API is stable, and performant(there was a performance assessment for the API in the past https://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=1383839)
2) or data-export performance as-is is a hindrance or not acceptable
3) The new changes needed to the hierarchy API are worth the extra effort

Until the above points are confirmed we are going to put this effort on hold

Fields that are not supported by hierarchy API:
1. All metadata fields for holdings and items;
2. In holdings statements, staffNote fields are not present;
3. Item notes - staff only are not present;
4. For all locations, code present for locations, but not present for campus, library and institutions;
5. Looks like an effective location for items are not present

Also another thing to note while using this API is that, in the future if we need any other fields to be added for export, we need to change the inventory-hierarchy API to support those fields.

The missing location code is a deal breaker so we will need to update inventory-hierarchy API to provide this information.