No, because then you need to track the timestamp in the db and append it to the image handler url with every request. Which also means third party apps can't easily access the pic based solely on userid. Well, they could but then they have to deal with the caching as well.

The proper fix is to remove the caching headers from the profile pic handler, which will be in the next release.

as a brief aside, i edited the resource file and used HTML to boldly enforce the need to refresh and thus far NO complaints. I bet most don't read it until after their upload seems to go wonky , but at least i have minimized admin calls!