Basically the main reason why Secure Erase leaves traces on SSD's is because SSD's have more capacity than they're showing to the OS. The rest is spare blocks that are being used for the wear levelling, so each cell is written to as randomly as possible even if you're constantly updating the same file. It uses the spare space randomly all the time so the same blocks aren't always spare.
But anyway, there is no way to read from the spare blocks through the OS. If you zero out the whole drive, the OS will only read back zeroes from then on. The spare blocks will be marked invalid and will be overwritten again before it ever tries to read them again.
Only by actually unsoldering the NAND chips and connecting them to another controller could you get any old data left on the spare blocks. Mind you, this will only be fragments of what was originally on the drive, most likely not even complete documents.
The way I understand it, is that it will take a team of forensic investigators or data recovery professionals days to scrape any useful data of whatever's left. So yes, you could get some data off it but it's not practical, and requires destroying the SSD. There might be some SSD controller hack to do it while it's in the computer but I don't think these are common.
It all comes down to who you want to protect your data from. If it's just some family photos you want to hide from the next buyer, you should be fine with a secure erase, and if you're still worried you could use the multi-pass one because that has a good chance of hitting most of the spare blocks as well, especially when writing random data. (I wouldn't do too many passes to avoid wearing out the SSD though! I'd say not more than 3).
So it only matters if you want to protect yourself from a criminal investigation, and in that case I don't even want to provide advice to you
