Thanks to this discussion, I came to think about a new feature using the zone priority:
Using the zone priority as a marker that identifies a zone as a teardrop. In this case, I would use a very high priority number that would also be a teardrop magic tag.
This would suppress the need for an external file that stores the teardrops definitions.
This would also allow single teardrop deletion by simply select the teardrop and hit the DEL button.
The user will also be able to modify the zone shape using the kicad zone tool.
The scripts will still provide the setTeardrops and removeAllTeardrops function untouched.
I know that this is a very dirty solution but I think the benefits are very attractive.
Since some people here are using this script, I prefer asking before breaking everything.