Is HTML5 Canvas really needed?

I'm getting warnings (from a browser plugin) that javascript in the environment_indicator module is making use of HTML5's canvas element. People occasionally do make reasonable use of this, but in practice 99% of use is for browser profiling in order to do an end run around the user's browser restrictions on Cookies. That would be out of line with my client's privacy policy, so I was concerned.

I'm seeing the following calling stack:
modules/contrib/environment_indicator/tinycon.min.js?o317b3 line 8 column 3352
modules/contrib/environment_indicator/tinycon.min.js?o317b3 line 8 column 2162

I don't care to pore through minified code, but I'm guessing this is based on https://github.com/tommoor/tinycon/blob/master/tinycon.js give or take a version. Without looking in a huge amount of detail, it seems that manipulating the favicon might be a legitimate use of a canvas element.

That said, association with the usually-suspect Canvas is unfortunate, and will periodically raise questions, and it's hardly the only way for this module to modify the favicon. Would it be possible to changethis module so it dynamically generates (and presumably cache) the different favicon images server side, and adjusts the favicon link on the page accordingly?