Yeah, I meant to say that ParaView cannot support this using CGNS files (I did not phrase my reply correctly).
I could use a different file format, though I would need one that includes metadata (i.e. Simulation Time).
However, for the time being, I could make do with one CGNS file per written instance, loaded into ParaView as a file series.
It is, of course, not a single file (which was my initial request), however it seems to work fine for now (given that the “official” CGNS way of writing the adaptive mesh is not compatible with ParaView).
So instead of having a single CGNS file with multiple zones and one time instance per zone, I create one CGNS file per instance.
With the correct metadata information (simulation time), ParaView opens the CGNS file series and displays things correctly.
I have one last question:
Can I create a file that behaves like a .pvd file, but using CGNS instead of VTK/VTU/VTP?
Like the following example which utilized .vtp files, with corresponding paths being defined into a master .pvd.