The HAF documentation says (https://gitlab.syncad.com/hive/haf/-/blob/develop/src/hive_fork_manager/Readme.md#important-notice-about-irreversible-data):
Important notice about irreversible data
⚠ Although reversible and irreversible block tables are directly visible to apps, these tables should not be queried directly.
As I see in the code all indexes are created on irreversible blocks data tables. Looking at the views they also are created on the irreversible data. Are You sure that new indexes are required additionally to those that are already present in HAF ? Without using views incorporated in the HAF You won't be able to present together irreversible and reversible data (live data). Please let us know if HAF is too slow for Your application, You may add a new issue. Maybe we can incorporate some changes directly inside HAF.
Reversible data won't matter in this case. If it was necessary we can add them to the views and it's not a big deal. Indexes are not necessary on the reversible data though as the data is too small to be worth creating an index for it.
The created indexes are necessary for this app but I don't think they are necessary for the haf itself since they won't be necessary outside this use case.
IMHO haf should stay as generalized as possible and don't put the burden of every single app on the HAF node operators unless they choose to run that app.