Dustin Aubrey I want to block sites like reddit during work hours, but sometimes reddit has the answer to a work-related question. It'd be great if I could limit sites like reddit to three visits per hour, so I could view that answer but not get sucked into reading all the posts.

You can certainly look in logs and click on details to see which list(s) blocked what you need and then you either add to Allowlist or disable the list(s).

You can certainly do everything from the phone.

You don't need all the lists enabled, most are redundant.
A few good ones is all you need. I use 6/7 depending on device. Some use less.

This is very relevant:

"Allowing a domain will automatically allow all its subdomains. Allowing takes precedence over everything else, including security features."

So, I added here what I temporarily need.
After I finish, I toggle off.

Also if something I need is blocked by some list.

An alternative solution is to create a new configuration (not account) without blocking lists (or minimal protection) and change the DNS to this one when needed.

I get it that are some cases when this function will be useful but some comments make little sense.

Speaking of comments that make little sense, I think you missed the point @jeff was making.

Jeff said:
A selected filter was blocking a particular banking app on my phone from connecting. 

 Jeff said:
A quick toggle would go a long way to at least make working around these issues faster and easier.

It seems to me they are describing a moment when they needed to do some banking and needed a fast and easy way to get through the blocker. It's great that there is a way to handle this case, given enough time, but I think it is a rash assumption that folks always have the time to dig around through logs at any given time. Also, while allow-listing a domain includes it's subdomains is a critically important feature and a great callout, my experience suggests that these situations are almost always caused by obscure domains. I sincerely doubt that wellsfargo.com, or whatever, is in a tracker blocklist.

FWIW, run-your-own solutions like PiHole and AdGuard Home do offer a simple toggle switch.  So, @Jeff, you may consider using one of those solutions until nextdns covers your use case.  Usability matters!

So instead of fixing the problem your idea is to leave yourself exposed.

You would get the same result by turning off the app or private / native DNS.

Yes.  That is, quite literally, what this entire thread is asking for -- the ability to "Temporarily disable filtering".

Maybe when you are alone that is using the particular setup, but most users (I belive) have more than one device behind the setup and disabling NextDNS in a suggested way would also expose all of those devices.

Also bear in mind that when doing so, you also need to flush DNS cache on your device to make it work.

I can see that best and the only way is that you use NextDNS client on a device or YogaDNS and disable NextDNS over those.