How does Firefox 145 affect CanvasBlocker?

[IngEyn]

With the recently released update 145, Mozilla added some fingerprinting protection to Firefox as stated in the link below. As mentioned on the readme page, CanvasBlocker shouldn't be used in combination with other fingerprinting protection settings or extensions. I went over to the test page and tried some combinations, which ultimately led me to believe that Firefox and CanvasBlocker alter (some) of the APIs in different ways, so I was wondering: How do these new changes affect CanvasBlocker and how should the average user calibrate the extension so that both systems can work without any overlap? Maybe they could and should be used together and maybe the default CanvasBlocker settings should change for 145+ users. I've noticed that Firefox is changing the Canvas 2D and WebGL APIs not by putting some kind of noise into the values, but by altering the reported values by fixed amounts. How would you rate that approach?

Hoping to reach the developer here as they haven't updated the extension for quite some time (maybe because it's just fine the way it is) but I am curious about if the Firefox update has changed some parts of the extension and wanted to point it out.

Link to the Firefox docs: https://support.mozilla.org/en-US/kb/firefox-protection-against-fingerprinting#w_suspected-fingerprinters