No matter who provides assets for a library will need to go through the full verification process. This includes us librarians! We never ever merge our own work, there always must be a second librarian involved who checks it. (And it is really rare to have something that can be merged right away unless it is generated with one of the trusted scripts we have. It seems there is always something that is overlooked by the contributor, no matter how experienced they are)
However, anyone can increase the speed at which something is accepted. One important part is to provide all the necessary documentation for the verification process. This includes not only the documentation of the component (datasheet, dimensioned drawings, …) but also documentation about the created asset itself (at least a screenshot of the asset as it is in KiCad, for footprints ideally a dimensioned drawing, for symbols the pin list)
And very important, every contribution must follow the same set of rules. There will not be an exception just because somebody pays for it. If you need an asset different than the rules require, then you will need to do so in your own personal libraries.
And a potential complication right now is that EVERY contribution MUST be made with an up to date nightly build of KiCad. Which might not be acceptable by commercial users.