Forgive me, are you trying to get an export of devices that require mapillary coverage?

Or are you trying to edit osm to add the relevant mapillary tag, by doing this query and tagging the map where it is possible?

In the second case, it is not an automated edit. So you can go ahead and do it as any armchair mapper could. You could cite source: Mapillary (along with streetlevel imagery) in your changeset comment and explain what you did there. It will automatically say what editor you used. You do not have to explain your workflow.

My suggestions:
It’s been encouraged to use just the image key, rather than the url as the value for mapillary in osm. The image key should never change, and presumably is requested via an API rather than through the website, making it easier to integrate.

e.g. mapillary=MfEfU0jdHULiSROiCvl0Wg

The url can be put under the image key
e.g. image=https://www.mapillary.com/app/?lat=52.626783214558486&lng=-0.9952875506141936&z=17&pKey=MfEfU0jdHULiSROiCvl0Wg
or image=https://images.mapillary.com/MfEfU0jdHULiSROiCvl0Wg/thumb-2048.jpg

Years ago, OSM would ask you to add a source=* key for an item, but when they added changesets, they ask that source attribution is added there. So as you finish a changeset in OSM, use the source tag, and include streetlevel imagery and also mapillary.https://www.openstreetmap.org/changeset/62778421 as an example of how i’ve done this in the past.

Using overpass to locate defibrillators and then adding the mapillary image is fine. You should attribute the source as mapillary and streetlevel imagery in your changeset as that is what you are using to refine the data.