IndexOptimize on VLDBs with tight maintenance window

Our team has started to use IndexOptimize to replace our current index maintenance solution. We have a tight two hour maintenance window to perform our index maintenance, so on our 1TB+ databases often the entire two hours is spent returning fragmentation levels from sys.dm_db_index_physical_stats. When the two hours is up no index maintenance has actually been done. Has anyone encountered similar issues and come up with any good workarounds for this while using IndexOptimize? We've considered using one job to execute IndexOptimize with Execute='N' before the maintenance window, and a second job to run the commands in the CommandLog table from the first job run. I'm just not sure the best way to automate that. I would greatly appreciate any suggestions or recommendations!