iirc (i am not deep in that topic), this format is used by many todays PGP implementations.
supporting arbitrary, maybe legacy, secret keys is not a primary goal and is always weighted carefully - eg. a larger codebase also means more security risk here. not to speak about implementation and maintenance effort.
Delta Chat is definitely capable of importing some keys, so without additional information on the type of the key, how did you export it etc. it is not possible to reproduce the bug.
I believe I am currently exporting Ed25519 and Cv25519
at once
gpg --armor --export <???>
The resulting .asc file has a “public key packet”, a “user ID packet”, a “signature packet”, a “public sub key packet”, and a second “signature packet”. I am very much out of my element right now.