Yeah, it definitely makes browsing a lot more hands-on, and the lack of cross-device syncing means that you’re constantly duplicating work. There’s probably a way to export settings and diff/patch and sync the settings files for each device, but I just haven’t bothered; seems like a lot of time investment to automate something that takes me seconds to do manually.
On the other hand, there were two big shifts for me after I started using it. One was when I got the sites I use frequently all set up after a few weeks, it became a lot smoother sailing after that. The other was when I finally took the minute to find the setting to default (temporarily) allow, but only for the current domain (after like a year or two on default deny everything).
It’s now rare that I visit sites where I feel like I’m missing out without the added scripts. The only times that has really changed is when everything started implementing anti-scraper measures, and sites along the high seas that have trouble streaming videos from other servers.



I have it on all my home networking equipment, my router and my APs, and a wifi bridge for my SBCs. My experience has been that it is just as simple as the proprietary firmware, and more robust. The catch is that I chose each piece of equipment knowing that I would flash custom firmware onto it, so they were ones the OWRT wiki showed as being simple to flash.
Which model TP-Link are you going with? The page for whichever model on the OpenWRT wiki should tell you whether it’s easy or difficult to flash and revert