Yeah, if someone volunteers to test these and post the outcome, it would be amazing! Maybe you can do it @hurmo? 
I'd say stick with what you're familiar with, unless you have time/desire to experiment with and learn about other packages.
I'd also like to point out that https-dns-proxy can also be considered an ad-blocking package -- you can use any of the ad-blocking resolvers and for some of them there are customization options to pick and choose what specifically you want to block. And the beauty of it is that you don't have a powerful router with a lot of RAM to use ad-blocking.
Update on 2024'04'22:
While I was working on this reply to a generic OpenWrt name resolution question, I've realized that there's one pretty substantial difference between the three packages mentioned by the OP and even https-dns-proxy when used with the adblocking resolver. The adblock contains the collection of the block-lists curated by author, from the glimpse at the README they are even grouped into categories. If you use adblock-lean, the pre-made block-list (or rather the dnsmasq-config file) is curated by whoever produces/maintains the list. Similar with the https-dns-proxy you can select the adblocking resolver (some may be customizable to a point), but it's essentially what the DoH resolver selects for the block-list.
The goal/design of the adblock-fast is to allow the easiest customization so you could add/delete the blocked or allowed domains/lists, however if you want the curated/categorized lists, you may be better off using adblock or https-dns-proxy with customizable adblocking DoH resolver or if you just want to use the prepared dnsmasq-config file, you can use either adblock-fast in non-processing mode or adblock-lean.