Ok, I have fixed it by manually applying offset 48. (to confirm, I tried both -48 and +48)
Interestingly enough, AccurateRip wasn't matching with the "bad" rip, even offsetted:
[AccurateRip ID: 0010dc8f-00a07b17-ac093e0c] found.
Track [ CRC | V2 ] Status
01 [6ad7d846|1b70bc01] (0+0/4) No match
02 [f610bde3|308faad8] (0+0/4) No match
...
11 [d5ec9590|b84a3f4a] (0+0/4) No match
12 [249d0cdf|b9977aa8] (0+0/4) No match
Offsetted by 48:
01 [6ee04315] (0/4) No match (V2 was not tested)
02 [1d194b33] (0/4) No match (V2 was not tested)
...
11 [398b030b] (0/4) No match (V2 was not tested)
12 [49eba09b] (0/4) No match (V2 was not tested)
... but with my "fixed" rip, it did match:
[AccurateRip ID: 0010dc8f-00a07b17-ac093e0c] found.
Track [ CRC | V2 ] Status
01 [6ee04315|1588843b] (0+4/4) Accurately ripped
02 [1d194b33|4f97edd0] (0+4/4) Accurately ripped
...
11 [398b030b|1d5aaa94] (0+4/4) Accurately ripped
12 [49eba09b|df7b53d6] (0+4/4) Accurately ripped
(also, before verifying, I try with removing EAC log files, etc. from the folders, to not "hint" CueTools)
Long story short, my rip is fixed and I'm happy.