I haven't noticed any abnormal behavior, but I also don't mount/luksOpen them with -o discard (if that's what it takes to trigger this).
Weird. That's interesting. Why did I think WD and other companies would just keep churning SATA interface drives forever and ever.
Seagate's 3.5" Backup Plus Hub drives mask the disk itself intentionally to show itself as a different, generic Seagate device, probably to prevent people from messing with the disk settings and identifying the disk itself.
In addition to devices, the host controller has to support UASP too - in early days of USB3, it was separately licensed option.
At best perhaps it's a method of enforcing product segmantation - preventing users from buying & shucking what are strangely cheaper external drives (discounted so that WD can sell you (or sell 'you' via telemetry) some value addon software. I don't see a technical reason for how a drive could physical be unable to support this SCSI command.
But I don't understand how them maybe not being top quality would make part of the SCSI protocol disappear in the firmware. That indicates that these drives had a different firmware developed for them with missing features which makes no sense.
They implement certain parts not pass through and do indeed have separate USB firmware.
Don't ask me how I know this.
Also they have a lot more tolerance for disk failure than almost anyone.