If I understand correctly:
Before PR:

1. The game saves at the exact scene where the player was when exiting, if autosave is enabled (regardless of autosave interval).
2. Except for the cutscenes, for which it would save right after (the moment when interactive mode returns), if autosave is enabled (again regardless of autosave interval).
   Progress lost: The rest of the cutscene, and apparently in some cases it also lost the interactive part of some of those cutscenes (?) Like the Ghen one near the end (I've not tested that specific one, I'm going by the ticket description)

After PR:

1. The game saves at the exact scene where the player was when exiting (if autosave is enabled).
2. Except for the cutscenes for which now it does not create a save at all (if exiting while the cutscene in still ongoing).
   Progress lost: Everything since the last (auto)save up to the cutscene. This could potentially be a long period of progress lost. But in this case the user loses something that they experienced, rather than misses out on content they did not experience.

Is this a correct summary?

Would it be possible to save just before the cutscene plays (when autosave is enabled) so the user loses minimal progress?

Is this a correct summary?

Yes. And just to clarify, currently exiting a cutscene containing an interactive component produces an autosave which displays a misleading thumbnail image of the exact scene at the time of the exit call. However, when launched, the saved game always begins after the entire cutscene is skipped, the same as a normal cutscene.

Would it be possible to save just before the cutscene plays (when autosave is enabled) so the user loses minimal progress?

The million dollar question! It's something I've often thought about, and would be a great improvement, but I simply don't know. And since the departure of bgK from the project, I'm not aware of any other devs with enough knowledge of the engine to reliably answer that question.

Nevertheless, it's not all gloom and doom. The user always has the option to manage the situation by selecting the minimum autosave interval, and accessing the main menu indicates that saving is disabled, so the user can opt to delay the exit at their discretion.

As is, and since it is the intended behavior, the PR looks good to me too.

Thanks!