Given that the DHCP menu hang seemed to come about only when the Puma 6 latency flaw got fixed, I wonder if that is the price we have to pay for that fix, and the poor UI performance was regarded as an acceptable form of collateral damage? It would be very surprising if there were no consequences of shunting the processing load between the Hub 3's various chips.
If that is the case, then I suspect most of us would prefer to have the current latency performance of the Hub 3 and tolerate the poor UI performance. In an ideal world the Hub 3 would never have been an Intel-based product (and in the same ideal world the new Hub 4 would not either, and would have had self contained speed testing, and automated "phone home" for out of spec diagnostics, it being 2019 and all that....). But I think we have to accept that all ISP hubs are minimum-acceptable-spec, cost-engineered mediocrity, and the ETA of this bug being fixed is probably twelfth of Never. Digressing further, I think that with the Hub 3, VM walked into the trap, albeit they ignored the warnings from their own user testing in preference to telling Arris to take a hike. But the mediocrity of the Hub 4 shows that the company learned nothing from the Hub 3 experience. Virgin Media's procurement people are evidently like cynics the world over, and know the price of everything and the value of nothing.