There is one issue right now, despite having exceptions[] = {"notOnMap"}; in config the interaction is visible on the map screen (wanted to hide it there to not clutter the map interaction).

It works the other way around, you don't want "notOnMap" to be an exception for the canInteractWith check.

Exceptions are double-negated. In this case "not not on map", resulting in "on map", meaning also show on map. Just remove it as mharis said.