Gcode, postion printhead relative to part

My basic question:

Can I tell Octoprint in a Gcode script (in my case the "After print job is paused" one) to move the printhead to a specific postion relative to the part currently being printed?
Like I can do in Prusa Slicer with something like "G1 X{first_layer_print_min[0]-10} Y{first_layer_print_min[1]+2} Z0.8 F6000.0 ;". Just that there unfortunately is no option for a custom Gcode for before resuming a print.

What is the problem?

I have set up a custom Gcode script that homes the X axis and moves the bed forwards a bit when a print is being paused, so I can more easily reach the printed part (for inserting magnets for example) or so I don't have to change the filamtent right over the part.
Now after resuming the printjob, the printhead goes very slowly back to the position where it needs continue printing, happily oozing along the way, smearing filament over the part and then when it actually starts printing the nozzle isn't primed anymore at all. It doesn't seem I can tell PrusaSlicer to write in the Gcode to make this move faster, so only manually editing every Gcode would be an option.

My current pause script:
G91 ; Set relative positioning mode
G1 E-20 ; Retract filament by 20cm
G1 Z20 F180 ; Lift Z-axis by 20mm
G90 ; Set absolute positioning mode
G1 X0 Y140 F150 F9000 ; home X axis, present print

My current "resume" script:
G28 X Y ; Home X and Y axis
G91 ; Set relative positioning mode
G1 F3000 ; Set feedrate to 3000mm/min
G1 E25 ; Reverse retraction of filament, +5mm
G4 S15 ; Pause for 15 seconds, for cleaning the nozzle
G1 Z-20 F320 ; Return Z-Axis to original position
G90 ; Set to absolute positioning mode

What did you already try to solve it?

Websearch only gave me unreleavant results for relative positioning.

Systeminfo Bundle

octoprint-systeminfo-20250128235411.zip (191.1 KB)

Just to be sure - the parking works with normal speed, right? Just resuming is slowed down?

Seems so.
Pause: Proton Drive 9 seconds
Resume: Proton Drive 34 seconds

Parking is being done through code in Octoprint. Resume is essentially from PrusaSlicer, and I guess it is simply assuming the print head still where it left it. So why bother moving fast…