I'm not sure what you mean by "in another profile". Please open an issue at https://github.com/kkapsner/CanvasBlocker/issues with an exact description of your suggestion/request.

This kind of behaviour was already seen but could not be reproduced in FF 73. Please add your system information at https://github.com/kkapsner/CanvasBlocker/issues/388. This issue is currently closed but can be reopened.

If something was faked on a page a fingerprint icon appears in the address bar. By clicking on you see more information and you can also whitelist the page there.

The same issue is discussed at https://addons.mozilla.org/de/firefox/addon/canvasblocker/reviews/1141570/ and https://github.com/kkapsner/CanvasBlocker/issues/154

In short: it fine to have these sites to report a unique fingerprint as long as the fingerprint changes (which is the case in the default CB settings). You can open up the console (Ctrl + Shift + K) and have a look at the actual fingerprint. There you will see that the protected fingerprints change with each reload.

Regarding support: github is mainly a code managing service (you can look at the complete source code and history of CB there). But it also offers a requirement and bug tracking feature. As I am only one person I have no time to give individual email (or even phone) support. On github some helping angels can support me. Also it provides an overview of already asked questions and open issues so other people with the same issue can see that it is known and/or what the solution is.

In the default settings the canvas fingerprint is changed on every page reload (you can test that on http://kkapsner.github.io/CanvasBlocker/test/test.html). Yes - this makes the fingerprint unique but since it is not constant you cannot be tracked.

If you want further information/discussion please open an issue on https://github.com/kkapsner/CanvasBlocker/issues where we can communicate nmuch easier.

PS: similar issue on github: https://github.com/kkapsner/CanvasBlocker/issues/154