Those daemons started very early are special, they don't start working until the interface is configured to use them. I'm not sure it's an appropriate place to run dhcpcd (and hacking /etc/rc to do it is definitely less than ideal).
Of course I wish I didn't have to hack rc(8); but until dhcp6leased(8) integrates IA_NA, I'm stuck with non-base daemons. Admittedly, dhcpcd is pretty high quality with good privsep; so it's not a big deal to me. Also even if dhcp6leased(8) added IA_NA, I'd still have to hack rc(8) to move where it is started since it's started too late for my use case. Also one benefit of using one daemon for both DHCPv6 and DHCP is easily ensuring the same DUID is used which is both recommended by RFC-I-forget and required by certain ISPs.
Is it any better if you do e.g. <whatever other setup> up !rcctl start dhcpcd in the relevant hostname.if file?
Ah, haven't tried that. Maybe I'll change my setup to that instead.
Sounds like 10.0.10 in 7.6 release was no better for you either then and updating it to 10.1.0 helped Courtney.
Not only was it not any better, it was worse due to the PD-renwal bug.
Happy to backport if there's an upstream commit re this. But I'd rather not do that until then.
I agree you should wait until a commit fixes the problem. I will report back when that happens.