DHCP is ok for floating devices, or monile/portable - but having DOES management on a larger LAN for a while, it's a NIGHTMARE when you're trying to figure out what the address for a device that FAILED is. MAC addresses are noticeably longer than IP addresses, it's a ton easier to make a mistake reading them - even if you put a note on each machine with the MAC address.
Also, MAC addresses are sorta random (yes, I know about the "manufacturer number" part) while you can assign an IP address yourself in a logical way, like "by rack/shelf/location on shelf" which makes it TRIVIAL to figure out what the address of a failed unit is even if you didn't remember to put a note on it.
Unless you're shifting stuff around a LOT, thre's no REASON to "change an IP" once you've set it. You set it once, it's THERE.
DHCP on a LAN full of non-shifting devices is for the birds.
Why do you have to worry about "various types of interface" when you set a static IP? That seems to be a totally strawman comment.
It seems like you move hardware around a TON more than any network I've ever dealt with, which would make your environment completely different than what I've worked with. My experience is that DHCP makes things a royal PAIN to deal with, STATIC makes them a ton easier.
I use MAC Adress as worker name.
If you want to sell miner, you have anyway switch to DHCP before shipping.
