Only self-heals that happen from self-heal daemons are shown in 'gluster volume heal info *' commands. Even gluster native mounts, nfs server processes can do self-heals whenever the files/dirs accessed through them.
The self-heals successfully done by mount/nfs-server processes are not shown in the 'gluster volume heal info healed' command.
Workaround (if any):
It is always better to fix the files as in when the file is accessed to reduce the probability of going into split-brains but if the user wants to manage the self-heals only through self-heal-daemons the mounts/nfs-server processes should be configured to not perform self-heals.
So the user needs to set
gluster volume set <volname> cluster.entry-self-heal off
gluster volume set <volname> cluster.data-self-heal off
gluster volume set <volname> cluster.metadata-self-heal off
Once these options are set, Until self-heal-daemon fixes the file there is a chance of the source brick (brick with actual file contents) going down before the file gets a chance to heal and probability of ending in split-brain if the file is written to after the source brick is taken down.
The user will be able to observe the functionality he requires, with the work around suggested.