I think it will be relatively hard to pass f-droid's policy for now since there are still quite a lot google dependencies. The most significant parts are some binaries in building tools, and the denpendencies on play services.
I believe the Bromite authors had the same problem so they set up their own repo, but if those dependencies can be completely removed then sure we can add this to f-droid.
The biggest issue was to build the massive Chromium codebase with F-Droid build system; you can start reading from https://github.com/bromite/bromite/issues/4
There is also https://gitlab.com/fdroid/fdroiddata/merge_requests/3351 which was started because Bromite was not on F-Droid and without the binaries you mentioned.
I have read both and the VM problem is really a pain. The whole approach looks messy to me and their Debian is two major versions back so I am not sure it is a good idea to put effort into that.
I have already cleaned out most of the binaries in build tools, but the jar/aar dependencies are still a problem. I shall begin import patches from that build you mentioned soon but I need to setup a debug environment first.
Deleting a branch is permanent. It CANNOT be undone. Continue?