In my project I have a pipeline to use a custom binary file that I generate based on other software files (aseprite, tiled, photoshop, etc...). This allows me to have a more dynamic workflow, specially when making constant small changes.
If I use a png file, my workflow would be:
Aseprite --> Export to png --> Load the data into my project --> Use
The workflow solution above results in two files with the same purpose (if you don't forget to export every time you make a change). Using source files, it is:
Aseprite --> Load the data into my project --> Use
Resulting in only one file and without the mentioned export problem. This may seem very specific for my case, but considering that popular game engines such as Game Maker, Unity and Godot have plugins that allows this kind of usage, I think it's a valid point.
That is not a big problem when working with few files, since I can open the png file in Aseprite and save them again, but when doing it for every hairstyle, in every color it's starts to become a little boring. Not to mention that I presume that you already have and use the .ase files.