How to deploy simultaneously several critical bugs with gitflow process as soon as possible? : So we use the gitflow process for a safe and sound CID
(https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)

But something's wrong..

Lets say we have 10 critical bugs on prod - they must be fixed asap.
So 10 bugs are assigned to 10 devs.
Dev 1 creates a hotfix 0.0.1, commits the fix to it, fix gets uploaded to staging env and handovered to QA for verifing.
In that time dev 2 wants to create hotfix 0.0.2 for his bug, but he cant as gitflow forbids creating new hotfix if one exists already.
So he either have to wait for closing hotfix/0.0.1 or commit to the same hotfix. 
Of course the normal choice is to commit to that hotfix/0.0.1, because his bug is critical and cant wait fix for bug 1

So does every other 10 devs with their 10 critical bugs.

QA verifies bug 1 and confirm for deployment.
But hotfix can't be closed and deployed, because the other 9 bugs are not tested or just not working

So to be closed, every bug in that hotfix must be working and confirmed.
In our case this takes time, a lot of time - 1,2 weeks, luckily
- as more and more things needs to be fixed asap on production. 
So devs commit to that branch more and more, getting the first bugs to be put on hold even more.

So eventually, after all those bugs are fixed and confirmed it is time to finally close the hotfix and deploy those critical bugs on prod...with quite of a big time delay.
But there is also another big problem - THE MERGE with dev branch, where other devs do their work (like minor bugfixings for next release). A horrible, several-hours lasting merge.

So we obviosly do something wrong...what could be a solution for this? 
For our hotfixes to be on time and to not have terrible merges to dev

One solution we were thinking, is to put a limit in the hotfix for the number of bugs which it should contain
 - for example 5 bugs max, other bugs must wait until those are fixed
This, though, means that only lead-dev should commit to hotfix, as he must ensure the limit (it is hard to control otherwise)
But this way bugs are still put on hold and fast-deployment is not achieved

What would be the normal procedure? Please share your ideas.