I may not understand SSD's all that well; still, I was under the impression that the controllers on SSD's are designed to ensure that there is no "10% of the drive that is used extensively".
No, the controllers on SSDs are designed to ensure that new writes are directed to blocks with lower write-cycle counts.
They do nothing to the files you've already got on the device, some of which will be in blocks with write-cycle counts in the tens or less.
Let me try it this way: you format a new SSD, and install an OS on it. Those OS files might never get changed, and will always sit there with a very low write-cycle count.
Then you start to fill the drive with a few pictures, files, etc. Those files may come and go, and will be in blocks which move into low-write-count -but available- sections of the drive as they're written.
The drive fills to, say, 90% full. Now, the temporary and short-lived files which were always getting written are constrained to that remaining 10% of free space - in effect, shortening the lifespan of the overall device by a factor of 10, in this example.
If you delete a few pictures, that space will be freed up again and will be used preferentially for new files (since it has a low write count). But it could be another picture that fills the space, or it could be temporary files. And there's no mechanism for selecting the blocks which have the shortest remaining lifecycle for a file which might survive a longer while. Instead, the mechanisms will tend to put the next picture back into the available blocks with the lower write count. So as the drive goes back to 90% it'll be mostly the blocks with the higher write count which are still being used for those temporary files, killing the device efficiently.