Better HID driver support
Better workstation experience
LibreOffice
Eclipse and other IDE
I remain of the (unpopular) opinion that GUI/DE use of FreeBSD is less important than the base system (CLI, server). If there isn't enough money and manpower for both, we need to focus on the latter.
Make INIT(8) faster
I insist, I write here MAKE INIT(8) FASTER (through parallelism?), not replace it.
On modern SSD-based machines, does it really matter? Can this be done without a major (incompatible) redesign of how services get controlled? Before we commit to this, let's measure how much we could save. And come up with a good design; parallelism is hard.
(Pkg) Provide a better mirror management
(behind a vpn, I can download faster with an US mirror than the EU one)
It seems to me that the root cause here is your VPN being configured strange. Let's fix that first, before throwing the baby out with the bathwater.
Add pkg new options: search -file
That seems like a good idea.
-no-recommended
Better “decoupling policy” in ports and packages
Part of the problem is that the user (you!) need to understand the difference between packages and meta-packages. The latter are intended to install a lot of stuff at once.
Another part of the problem is that package maintenance is done by volunteers, who may have different styles. Training and guidance might help here. As would ignoring problems in DE/GUI packages.
Try to get more “languages supported”
I18n and a11y take a massive amount of effort. Nearly all of it is used for GUI/DE efforts. This is in the "nice to have, but not vital" category.
Provide us unprivileged jail
What is the purpose of a jail? Privilege separation mostly. If you have just one non-privileged user, why would one want to do privilege separation? Please explain a clear use case for this.
The goal of these tools (whether it's docker, kubernetes, containers or lxd) is to make installation of complex software packages easy, by bundling prerequisites with the package. To some extent, they are a work-around for the balkanization of Linux distributions. To some extent, they are a work-around for continuous integration workflows, where you want to package a snapshot of the state of prerequisite libraries. None of these problems exist in FreeBSD, which has only one distribution, and uses a release workflow.
If your idea is to create ways to run existing Linux containerized packages on FreeBSD: Why? There is a perfectly good OS available to run them on (namely Linux).
Better documentation and Wiki
Where the handbook is outdated or incomplete, let's get it updated. It is an excellent form of documentation.
Host some ports inside FreeBSD
I agree that some packages are so commonly needed, and when needed so vital, that they need to be really well maintained. Examples include python, perl, apache, some databases (MySQL, BerkeleyDB, SQlite). But I have not seen problems with the maintenance of these crucial packages.
I consider Firefox mostly irrelevant. It is not a core function of an operating system.
The Power to Server", a failure?
I can summarize all your writing in this section as: FreeBSD has a very low market share. I don't see that as a problem. It is a very good operating system. It had a low market share 15 and 20 years ago, and hasn't died yet. A rush to popularity would be suicidal.