Network interface renaming

Hello.  I am booting a 14.3 amd64 router, and the network connections are
all vlan interfaces on a 10Gbe link.  I found some time ago that I can
rename these interfaces and decided to do so.  But, recently, I’m noting
that some things are not working properly at boot, including (but not 
limited to) local_unbound.  I fear this is because the interfaces are
renamed _after_ local_unbound tries to start using them.

I don’t see any log messages from local-unbound in daemon.log until
I manually start it after the system comes up.  And I don’t have a
full view of the boot messages as they’ve scrolled off of the screen.

1. Is interface renaming just too dangerous to use?
2. Is there any way I can make the interfaces take
their names earlier?
3. Can I verify when local-onbound, or other, daemons are starting
up and if they’re failing get that reported somewhere I can see
After the system is multi-user?

Thank you for your help.

         - Chris