You're basically on the right track. If you want Unbound to handle advanced features like DNS overrides, forwarding (for something like NextDNS), and also automatically register static DHCP leases, then Unbound needs to be the resolver that receives those host entries. With the legacy ISC DHCP, that integration can be limited or inconsistent depending on setup. KEA is designed to integrate more cleanly in newer stacks, especially in systems like OPNsense, where KEA can dynamically update Unbound via proper hooks. So yes, if automatic registration of static DHCP entries in Unbound is important alongside advanced DNS features, moving to KEA is usually the cleaner and more reliable approach.
"