We found the the reason for the error:
It was a wrong usage of the command "Add-DhcpServerv4Failover", this is meant to connect a whole server, not a single scope. But it allows you to do many connections to the same server, that is maybe a design flaw. It can spoil all of your 31 available connections on single scopes on the same server....
In fact, you can connect 31 DHCP Servers to your partner DHCP by using the command "Add-DhcpServerv4Failover".
And..You can add >200 Scopes per Server as you tested with "Add-DhcpServerv4FailoverScope" referring to the same name.
This command is initializing the Failover-Connection with 2 Scopes for example:
Add-DhcpServerv4Failover -ComputerName "server1" -Name "Server1-Failover" -PartnerServer "centralDHCP" `
-ScopeId 10.10.10.0,10.20.20.0
additional scopes from the same server must be added by this command under the same Name:
Add-DhcpServerv4FailoverScope -ComputerName "server1" -Name "Server1-Failover"-ScopeId 10.10.11.0,10.20.21.0
...The next Server gets a new connection name as communication channel "Server2-Failover".
Thank you Jiang for your efforts, i recommend using powershell doing such jobs...