I've never heard of anybody doing that, and nobody related to this project built that wheel so the answer from this point of view is - don't know.
We can however scope out the possible issues, expect some other surprise!
I'd be interested to know if you get it working.
The Python version is the same as p4a (currently - which is a potential long term support problem when the whl or p4a changes), - probably OK for now.
The 21 in the name is (I expect) min sdk, which is the same as p4a default - probably OK
Arm64_v8a whl, this arch is available with p4a - probably OK
One unknown is ndk version. p4a uses 19c and we don't know what the whl uses. If the wheel uses the same - great. If not there may be issues, 21d mostly works with p4a but there are issues with 21d independent of p4a, 23 is good but p4a support is currently in development. - so don't know how this will resolve.
And just in case those guys try to keep their whl proprietary :
Do the symbols use the default llvm symbol name mangling?
2) How to tell Buildozer to use that repository?
Buildozer downloads from pypi, it may be possible to change that but I don't know how.
I think you'd have to create a local recipe that downloads the whl and installs it in the apk site-packages.
That would be a simple recipe, but recipe writing help is non existent so you need to be self supporting.