Regarding the DHCPD: it is described in detail at this link. The issue is that your so-called solution cannot listen on two independent interfaces, nor can it run two separate daemons to handle these interfaces independently. This presents a significant security risk, as it requires trusting that you can effectively separate the two zones virtually. Based on my observations while working with your product, I do not have confidence that your company can ensure this separation.
In addition, your GUI allows users to configure two separate DHCPD for two independent interfaces, but only one configuration is actually applied (sic!) the second is ignored entirely, leaving users unaware of the problem. This is a fundamental issue, and I am genuinely shocked that it has been ignored for more than two months. Frankly, this gives me serious doubts about your QA&QC processes. The fact that such an obvious flaw has not been addressed suggests a lack of proper testing and attention to detail.
It is especially frustrating when companies like Cisco and even MikroTik clearly understand the importance of these configurations and offer solutions that support them. It’s difficult to trust that your company is taking security and quality seriously when such basic issues are left unresolved.