The second point is from the link you posted. Someone there assumed that Pale Moon for Android is modified from Firefox for Android which requires some Google's proprietary libraries, but it seems it's not true (The official API contains an optional part called Google APIs which can lead your binaries only work with Google's proprietary things installed). I would take back this point.
Point 3: I don't see how they treat Pale Moon as in public domain. But this is not the main point any way.
I really cannot agree with these -- F-droid is just similar to how Debian works in the sense that you can build everything by yourself, or use the binaries built by the build server maintained by F-droid people (A technical difference is that for Android you would probably need to do cross-build). Actually, F-droid makes it easier for apps to be built on users' OWN system.The difference is that F-Droid builds the app, then offers binaries THEY built with THEIR signature (not the software authors') for F-Droid users, pretty much having full control over the software and its distribution, update and continued publication, and treating the actual software authors as resources. Once an F-Droid version is installed on users' devices, only their version will be considered valid and users are immediately bound to F-Droid's operational practices (because a change in distributor, package name or signature would invalidate the install and people would lose their stored data when switching).
The MPL is a very good mechanism to prevent rogue copies and to have control over my binaries. The MPL specifically includes a clause that binary form may be distributed under a different license, which I am doing.
It allows free source redistribution and allows people to build their own binaries from source on their OWN system and adaptation to special needs, but prevent tainting of official binaries with modified copies in the wild.
I also give special permission to Linux distribution developers in the binary redistribution license to build their own binaries for their OS flavor in the redistribution license for binaries. Without that, only the user would be allowed to build their own copy from source (and only for their own use).
F-droid is not a traditional store which developers distribute software on their server; it stores some meta data which teach F-droid servers to build the binaries directly from the source. The server software and metadata are all FOSS. By submitting an app, it actually means to submit a metadata file that TEACHES THE SERVER TO BUILD from the source (which can be done not only by the author, but anyone else). This also means, YOU DON'T HAVE TO USE THEIR SERVER, YOU DON'T EVEN NEED A SERVER TO USE AN APP IN THE REPO. Just download their server software and metadata and you can build all the APKs on your own system by executing a single command, and you can sign it yourself. It's actually more trustable than using the binaries from the developers (think about OpenH264 and Cisco, would you trust it). It's not possible for them to take full control as a middleman -- assuming some day they become really bad, A different person can stand out and run the server software publicly. The reason that they provide a server to do daily building, per my understanding, is only for the sake of convenience similar to Debian.
If F-droid still looks bad for you after you have read the above, I would kindly make this request: If you really don't want F-droid people to distribute Pale Moon on their server, can you submit a meta data file (since you are the best one who knows how to build Pale Moon), and tell them that this app has a trademark policy and it should only be built by users for themselves (there are some metadata files they don't use to build on their server). Thus, we can enjoy the benefit that F-droid building system offers and no middleman would ever come for Pale Moon. Any way, thanks for your work done on Pale Moon and I appreciate it.