In the general case, we cannot know if innodb dataset is corrupted until applying the log.
MDEV-21109 there are pages which do not pass corruption test, but they are in free tablespace list, so it does not matter of they pass the test or not. We can't detect if they are allocated or not during backup, but we can do this during --prepare.
So we could log such allegedly corrupted pages during backup, and then try to fix them during --prepare. Particularly we could zero out pages which are in tablespace free list.
We should also think how to log such allegedly corrupted pages to make older mariabackup versions to refuse --prepare on dataset with the log.
We should also change documentation to reflect the fact that backup can be treated as non corrupted one if it is not prepared. We could stream backup, and some external tool can be used to upload it in some cloud. So the uploaded backup can not be safe until it is prepared.