I don't think it is so much a question of wear leveling or not, but what kind of wear leveling is implemented.
I suspect the industrial/heavy use ones have a separate per-sector counters and indirection, whereas the consumer ones that do have wear leveling use very simple algorithms with best-guess wear leveling without spending any extra resources on it. I do believe almost all SD cards have minimal wear leveling, perhaps some kind of linear congruential rotation of the sectors written, whose benefits vary depending on the use patterns from nil to excellent; which is why users have different experiences with the same card/series/manufacturer just by using a different hardware, file system, or OS version or firmware. Even minimal differences in (relative) timing can affect the effectiveness of such algorithms (because it affects the order in which sectors get modified).
This is a very annoying thing when trying to run an SBC off an microSD card, because manufacturers don't describe what kind of wear leveling they use, and it's almost impossible to tell whether their expected write cycle counts (TiB or per-sector) are realistic or just marketing wank.
In my experience, if you mount the card mostly read-only, they'll survive much longer; but for anything that needs more than occasional I/O, I use eMMC or SSD. If the SBC cannot boot off eMMC or SSD directly, then I use an SD card for the initial boot only.
Now that SBCs tend to have have USB 3, and there are cheap-but-okay USB-SATA controllers (I use a cheap Jmicron one on one of my SBCs), a small 240G SATA SSD (costs 30-40€ here) is an excellent substitute to those SD cards; and price range is similar to much smaller capacity industrial SD cards. The SSDs take a lot more room, of course, and consume somewhat more power, but the reliability is so much better compared to what luck I've had with SD cards, it's worth it to me.
I wish there was reliable info on the reliability/wear leveling of various SD cards, though. Sometimes one does have to use an SD card.