That is weird since it says the Drive supports SMART, but doesn't list any SMART Attributes or allow you to run the selftest. It's possible the drive doesn't really support SMART or part of it is being blocked by the drive's USB controller. I wouldn't trust the DriveDX results here at least for this particular drive.
If you still have the special USB driver installed, try accessing the SMART information from the command line using the Terminal app.
Within the Terminal begin typing this (make sure there is at least one space after "sudo ":
sudo
Now drag & drop the DriveDX app onto the Terminal window so it auto fills the correct path to the app, then continue typing the following (press the delete key to remove the extra space as you need to extend the path":
/Contents/Resources/smartctl -a -s on /dev/diskN | tee ~/Desktop/drivedx-results.txt
Where I wrote "/dev/diskN" you need to substitute the correct drive identifier for your drive. Use DriveDX to get this information. In the report you provided the drive identifier for your drive at the time of the report was "disk3". This drive identifier may change next time you connect the drive so check it before executing the command.
At the end of the line press the "Return" key to execute the command. Besides displaying the results on the Terminal window it will also create a "drivedx-results.txt" file on your Desktop with the same information shown on the Terminal window. Post the results from the "drivedx-results.txt" file here like you did with the original DriveDX report.
The final command will appear something like this (I used "disk3" as an example since it was in your original DriveDx report):
sudo /Users/hwtech/Downloads/DriveDx.app/Contents/Resources/smartctl -a -s on /dev/disk3
Edit: If you have a Windows PC you can instead try checking the SMART attributes using GSmartControl (there is a portable version that doesn't require an install). Post the full report here as you did before.
