When I re-enabled DHCP, the scope autonomously got its IP adress and NTP time. 
Sounds like Siglent still hasn't gotten DHCP right. Testing it, it looks like they're doing a DHCPDISCOVER roughly once a second, forever, if they don't get a response. RFC 2131: "The client MUST adopt a retransmission strategy that incorporates a randomized exponential backoff algorithm to determine the delay between retransmissions."
They also continue to ignore lease times, and do DHCP renewals every minute or so.
Ignoring lease time is reported and acknowledged but was not addressed at this moment. To be honest priority for that is low.
As for using backoff, one post up here is a very happy customer that is very happy that scope acquired address immediately after DHCP was available without delay.
Some standards are written while having in mind thousands devices in single LAN, and how to deal with chaos ensuing.
Single device asking for DHCP server like this is not really a heavy load. If you are not using DHCP then it doesn't matter. If you are using DHCP and server is not available, you need to fix DHCP server to be able to use network.
At that moment problem is fact that all your devices can't see DHCP server, not single device asking relentlessly.
I don't see scenario where this will create real problems.
I agree that formally this is not as it should be. In practice, this is not problem.
Make sure I will report this, but critical it is not.
Thanks for the checking.