Driver Updates in Intune

I feel like there are a lot of discussions on this topic, so I do apologize for throwing another one out there. I'm really trying to understand it all, but this tool seems like a complete mess. I realize that some of that could be the vendor's fault if they are improperly labeling things or labeling them very generically so that you don't even know what it is and have to do a lot of work to look it up and verify what you're even pushing out, but it's just so wildly inconsistent in general.

Sometimes BIOS updates are in 'recommended', sometimes they are in 'other'. I've read that if an update becomes superseded, it's supposed to move to 'other'. While that would make some sense, that also adds confusion and research time because it means not only do I have to sift through what some of these drivers even are in that section, but now I also need to determine whether they are even valid anymore. I don't want to approve an obsolete driver. I'd rather Intune just delete it from the list if they've already published a newer version.

Sometimes there are driver or firmware updates presented as the current one under recommended, even though there is a NEWER version with a later release date sitting there in the 'other drivers' section. In fact, right at this very moment, I have a BIOS update for my laptop (Dell Firmware v0.1.32.0) with a release date of 9/16/2024 waiting for my approval in 'recommended', yet also have v.0.1.33.0 with a release date of 11/14/2024 waiting for my approval in 'other'. Why? Shouldn't .33 be the recommended one?

We're primarily a Dell shop, so I'll probably just go with DCU, but this kind of stuff happens with a Surface device I'm testing with as well. Example:
I've got Intel - net - 23.60.1.2 sitting here in recommended, meanwhile I've got Intel - net - 23.70.4.1 sitting in other. It's a newer version. Why is it not the recommended one? I've got 6 different bluetooth drivers listed in other. They all appear to likely be the same driver, but 5 of them seem to just be older versions based on the version numbers (same major version number, different minor numbers). Why doesn't Microsoft remove the 5 that are no longer relevant?

I've had situations in testing where if an older version of a driver is approved and gets deployed, but the client already has it or has a newer version, it fails to install and just sits there in Windows Update for a really long time with a retry button, which of course fails again on every try. It will sit there for months on the client.

I guess you have to just set it to auto-approve and just ignore the 'other drivers' and never look at the profile again, and then it's great?