Journal Reverse Replication Commit

When initiating a “Failover” from Production site to our DR site (with reverse replication selected and committed), I notice that the reverse replicated disks are moved to a Zerto subfolder (from their original folder) but still on the same CSV volume that they where previously on – which is good.
I also notice that the journal is created for the reverse replicate VM, on the same CSV as the reverse replicated VM, when reverse replicating back to our Production site, is there any way to re-point the Journal log to a different CSV?

Reason i ask, is that our VM’s run on premium disk (All flash disk array on our Production site) and the Journals can get quite big, which would impact disk space on the flash array, we also have less expensive disk which would be fine for the journal, hence can i re-direct a reverse replicated VM to stage it’s journal on a different disk.