I don't know if someone will reinvent this, and if it has any chance to become popular. I wouldn't bet on it, but who knows...
I wouldn't recommend SOCKS either. Or even trying to solve this "problem" on a Mikrotik – focus on managing the bandwidth. If you need to restrict user in fine grain manner, look beyond the Mikrotik. But if you looking for novel Mikrotik approach that do something
to block website (how much YMMV), MT offer something
LOTS to do and try, but never be "definitive solution".
So more fodder for trying. At least SOCKS knows the always knows domain names, and if device/browser did support it, they probably respect any policy. DNS tricks are easy, but eventually avoided by clients. SOCKS5 at least be stable (eventually in V7), has a UI, and either clearly work, or not. Basically turn an SOCKS from yet-another-method avoid the very same MT content filters
discussed here (e.g. the force DNS firewall rules discussed here would do nothing if some DID configure their device to use SOCKS) – into SOCKS more historical form as the defensive gatekeeper. Start with a deny on all IPv4, then white list what doesn't work with SOCKS. Since blocking a one website is likely not the only thing someone might want to block.
What to do about IPv6 and block – this I'm more clueless – that seems even harder (but maybe easier). Sure there are some [likely partial] solutions out there. If you wanted to foist IPv6 usage, another idea along these lines is offering only SOCKS5 access for IPv4 is certainly an approach – allow you to focus your blocking effects on what to secure IPv6. More idea – since whatever you do in IPv4 firewall would have to be replicated in IPv6 firewall to enable it – making any block on a MT literally TWICE as much work. Since if you have IPv6 on the WAN, in most cases, you'd want to use it – outside being able to block websites, it generally offers speed benefits.
Also the other thing to consider is if you only have mobile device (Apple/Android), there may be easy/cheap ways to restrict websites. There is lots of Apple's MDM approach for iPhone and iPad, including using using Profile Manager
on a Mac - that lets you block website (and more). Android has similar stuff, again an expert. Also there are a lot of DHCP options that might be able to control some policy (can't think if web site blocking, but sometimes there are esoteric DHCP things to implement a network policy. Also believe there are Made for Mikrotik SaaS solutions out there that attack this same problem by applying these MT blocking techniques more automatically.
Basically a Mikrotik asking the network device to respect some protocol and block if they don't is different way of skinning this cat. You'd be looking for why something didn't respect. Or accept you may need to apply large org technique at the home to more realistically solve to do any website blocking effectively.