Bertho, welcome to the forum (are you the same Bertho from the Mach forum?)
It looks like CutViewer doesn't implement G92.1.
I wrote a little test program:
(Filename: g92test.nc)
G20 (Units: Inches)
G17 G40 G80 G90
(STOCK/BLOCK,4.0,4.0,0.5,0.0,0.0,0.5)
(TOOL/MILL,0.25,0,0.5,0)
G00 X0.5000 Y0.5000 Z0.1000
G01 Z-0.1000 F12
G01 X1.5000
G01 Y1.5000
G01 x0.5000
G01 Y0.5000
G00 z0.1000
G92 Y-1.500
G00 X0.5000 Y0.5000 Z0.1000
G01 Z-0.1000 F12
G01 X1.5000
G01 Y1.5000
G01 x0.5000
G01 Y0.5000
G00 Z0.1000
G92.1
G00 X2.5000 Y0.5000 Z0.1000
G01 Z-0.1000 F12
G01 X3.5000
G01 Y1.5000
G01 x2.5000
G01 Y0.5000
M30
and ran it through CutViewer:

- g92test_cutviewer.gif (4.64 KiB) Viewed 1184 times
and then loaded it into Mach3:

- g92test_mach3.gif (4.66 KiB) Viewed 1184 times
Mach3 processes the G92.1 but CutViewer doesn't.
I've never used G52, but with a little playing found that CutViewer doesn't process it at all.
It looks like, for CutViewer to correctly show your gcode intent, you'll need to (in the above example) replace the
G92.1
with
G92 Y2.5000
i.e. explicitly change the coordinate that was changed originally (I made a -2.000 change in the Y coordinate with the first G92 so I need to make a +2.000 change with the second G92).
Randy