I didn't misunderstand - you stated your goal was to create a DR solution, then brought into the discussion replication.
If the replication is for reporting, I would recommend looking at a read-only secondary instead. The only advantage replication has over using a read-only secondary would be creating indexes specific to the reporting requirements. That can be addressed by having a local database on the read-only secondary and using that database to host the data for specific reporting requirements.
In that scenario, you would run daily/weekly/monthly processes that build reporting tables in this database. This database also contains stored procedures, functions, views and other reporting tables that support all reporting requirements.
You have laid out an unnecessarily complex environment - just to support replication and then added AG functionality. That is going to be a nightmare to manage and maintain and I would not recommend it.