SSD: `badblocks` / `e2fsck -c` vs reallocated/remapped sectors

The badblocks utility allows one to find bad blocks on a device, and e2fsck -c allows one to add such bad blocks to the bad block inode so that they will not be used for actual data. But for SSD, it is known that bad sectors are normally reallocated (remapped) transparently by the drive (however, only when a write occurs). So, does it make any sense to use badblocks / e2fsck -c on a SSD? I suppose that * badblocks alone can make sense to get information on the health of the SSD, e.g. by considering the total number of bad blocks (I don't know whether smartctl from smartmontools can do the same thing... perhaps with a long test smartctl -t long, but I haven't seen any clear documentation); * it should be discouraged to use e2fsck -c (which adds bad blocks to the bad block inode), because due to the possible reallocation, the associated numbers (logical addresses?) may become obsolete. But there isn't any warning about the case of SSD in the man pages of these utilities. So I'm wondering...