That sounds like a good solution.  What's the make / model number of the card that you purchased?

Sorry... my error.  What I bought was a RAID controller: HP Smart Array P400 SAS PCIe Low Profile Controller w/ 256MB Cache

It used an odd connector for which I bought a cable to adapt it to up to 4 SAS drives.  I used it to wipe the drives.

I'll try later to see if CrystalDisk works with it.

Ah, okay.  Yeah, please let me know if you are able to get CDI working with it.

This card is supposedly an SAS passthrough card, so hopefully it will work with CDI.  https://www.amazon.com/dp/B002RL8IUO?ref_=pe_623860_70668520_dpLink  
I posted a question and got a couple of answers that seemed promising.  If you aren't able to get CDI working with your card, I will likely order this one instead.

normally the manufacturer of the SSD supplies also diagnostic tools
what brand are you buying?  samsung has the magician tool  https://www.samsung.com/semiconductor/minisite/ssd/download/tools/

Is this info not available under OMSA? You can set an alert for percentage endurance remaining so it must be able to collect the info from the SSDs,

https://www.youtube.com/watch?v=BdO0IhZyq8M shows how to configure Remaining Rated Write Endurance Threshold so Remaining Rated Write Endurance percent is probably under each individual SSD status.

Andyalder, no, drive health does not show up under OMSA or in the MegaRAID Storage Manager (which is what I typically use to manage Dell RAIDs as it is more granular than OMSA for that type of work).  I have an R630 with an H710 and four Samsung 1TB drives, and no TBW or health information is presented under the physical disk info (or anywhere else).  

David Johnson, thanks for the H310 link.  I'll most likely give one of those a try.

It turns out that the storage manager for the MD3820i SAN (which is what this particular batch of SAS SSDs is going in) does natively display SAS SSD health.  So we'll be fine in this particular situation, but it is important for me to find a solution (like the H310) that will allow us to check drive health without having a SAN nearby.

I ordered an H310 on Ebay.  The one in David Johnson's link was ready to go with the IT firmware already loaded, but it was $56, and for $25 shipped, I could get one that just needed to be flashed.  I figure this way I can test and confirm flashing the H310 to the IT firmware myself, and save a few bucks.  

I'll update this thread once I receive the card, and am open to more input in the meantime.

Try Linux with smartctl -that knows how to get SMART info from behind a megaraid

In hindsight, I should have bought the pre-flashed H310.  This cross-flashing process has been a huge time-suck, and I'm still not done.

I'm using this tutorial:  https://techmattr.wordpress.com/2016/04/11/updated-sas-hba-crossflashing-or-flashing-to-it-mode-dell-perc-h200-and-h310/

I first attempted the procedure using a tech PC with an MSI LGA775 motherboard, which recognizes and works with RAID cards in its PCI-E slot.  I was able to wipe the existing firmware using megarec.exe -cleanflash 0.  

After rebooting, I kept getting "ERROR: Failed to initialize PAL. Exiting program." when attempting to run sasflsh.exe.  This error is supposed caused by UEFI mode-enabled motherboards, or something like that.  UEFI isn't enabled or even supported on this MSI board.  I tried another tech PC with an ASUS LGA1150 motherboard, and ended up with the same error.  

Figuring maybe it was an issue with the FreeDOS install that's included with Rufus, I tried to use this tutorial to create a bootable Win98 command prompt.  https://blogs.technet.microsoft.com/csstwplatform/2012/06/25/how-to-create-a-ms-dos-bootable-usb-flash-drive/  Rufus refuses to flash the image to the USB drive.. I suspect it's because the USB drive is 16GB and defaults to FAT32 and won't allow me to convert it to just regular FAT.  So now I've got to try to find a small USB drive.

Okay, so I found a 512MB flash drive, which allows me to format it in FAT, but it says "this version of Rufus only supports bootable ISOs based on bootmgr/WinPE or isolinux.  This ISO image doesn't appear to use either."

The theoretical solution is to get an SAS HBA adapter, like the IT-firmware-flashed H310 that David Johnson suggested.  I bought a RAID-firmware H310 but could not successfully get it flashed to the IT firmware--my advice for anyone who needs an H310 in HBA mode is to just buy the pre-flashed one for $50 (on Ebay) instead of buying the RAID firmware version for $25 (also on Ebay) and attempting to do it themselves, unless you've got the time to spend fighting with it.  (Some people apparently get them flashed in minutes with no problems; not me.)

Anyway, I say "theoretical", because I haven't been able to get any of the 086DD 1.92TB drives recognized through an HBA adapter at all.   I'm probably going to make a new question on that subject.  

I was able to get a SuperMicro SAS2LP-MV8 SAS HBA to recognize a Kingston 240GB SATA SSD and a Dell / Toshiba 300GB SAS HD, and to read them using Crystal DiskInfo, so the principle seems sound.

Why do you not use smartctl with a Dell PERC? It does not need to be in HBA mode because the -megaraid switch works with PERCs although I haven't tried it on one since PERC6.

https://www.smartmontools.org/

Hard Disk Sentinel will also give the SSD wear percentage from behind a PERC.and that definitely supports all the controllers you mentioned in the question.
https://www.hdsentinel.com/compatibility_disk_controllers.php

I tried using SmartMonTools and.. I forget what problem I ran into with it.  

Per my other question on EE that I posted after this one, I was able to get the info from the drives by using a PERC 5i (a PERC 6i also worked, but an H700 and an H710 did not), configuring the drives into a RAID (doesn't matter what kind of RAID--drives just need to be part of some kind of RAID so they are accessible by the OS), and using HD Sentinel.  HD Sentinel provides TBW, health percentage, and a bunch of other helpful info about the drives.  

The one problem with this method is that the drives need to be configured in an array on the test bed computer (which wipes any pre-existing configuration info or data), so you can't just pull them out of a server, test them, and then put them back into the server.  It works best for testing drives BEFORE they are installed into a production environment.

If both controllers are the same you can import the whole array to test them.

Good point.  Unfortunately, that's unlikely to be the case--since the PERC 5i and 6i are older than anything that we're currently putting into production or are likely to have put into production in the last several years, it's unlikely that an array from a newer Dell controller would be able to be imported into an older controller.  (At least in my experience thus far--it's "easy" to go from an older PERC to a newer one, but not the other way around.,)