Starting HDR and using only level-0 backup vs (currently not implemented) using level-0 with incremental backups

For physical restore secondary of HDR, level-0 must be using. If you are using incremental backups from primary for physical restore on secondary, you get the error on secondary IDS in online.log:

...
11:55:36 DR: new type = secondary, primary server name = hdr_lo
11:55:36 DR: Trying to connect to primary server = hdr_lo
11:55:38 DR: Secondary server restored from a non level-0 archive - aborting
11:55:39 IBM Informix Dynamic Server Stopped.
...

Why IBM does not fix this behavior for possibility using incremental backups for physical restore secondary HDR?
If this feature will be possible, performance of restoring from this (incremental) backups become very fast versus retoring from level-0 and then rollforward many logical logs.

For example:
Server IDS A is primary of hdr, IDS B is secondary of hdr. On IDS A periodically (once a week) runs level-0 and bakup logical logs.
Suddenly secondary IDS B is crashed (for example, after 300 logs backed up on IDS A after newest level-0 run on IDS A).
Then for starting HDR between IDS A and B again, we need first physical restore of IDS B from level-0 and second rollforward all 300 logs on IDS B.
But if may be possible to restore from incremental backups, rollforwarding all logs between level-0 and level-1, between level-1 and level-2 will be eliminated!