Sometimes you can try to downgrade the vendor firmware.
Other option might be using serial and tftp to boot into initramfs and flash Openwrt from there but might need some experience, confidence and the fearlessness to be able to brick the device....
As far as I have understood with this D-link device family is that it pretty much became a dead end in the Realtek project when the signed oem firmware showed up.
And the Realtek switch dev tread is pretty quiet nowadays.
I already have mine running with Openwrt...
My comment was more ment in a sense that I have to stick with mine and not go out and buy another one from the shelf because chances are that it's now delivered with the new signed firmware version...
The main problem is that no one has played with >v6.30.xx so far. Everyone who has an older device with <=v6.20.xx installed shouldn't dare to install the newer OEM version, no one who got a newer device has done serious investigations about the new situation so far. The OEM changelog doesn't sound too promising, talking about 'encrypted' (probably signed) images - and it being impossible to downgrade.
Serial console access will be needed, maybe you can still get bootloader (or at least shell-) access that way. Reflashing the spi-nor system flash externally (with the old firmware) should be possible (but non-trivial), as the hardware itself presumably hasn't changed (significantly). Please document your findings, missing information is the biggest hurdle for these devices (and upgraded older ones) so far.
Only one thing is clear, the situation won't fix itself, unless someone who is 'blessed' with an affected device starts digging into it. It's not going to be impossible, but it may be rather convoluted.