For the short of attention span like myself, let me try to summarize.
From what is posted above, a kickstarter project would require:
-A well defined, fully detailed implementation specification document in advance.
-A definitive completion end date / consumable amount of time.
-The above prevents inclusion of maintenance.
-Project creator(s) should be the developer(s).
-Project creator's background/resume.
This implies it is likely a project would be rejected if it is perceived to be part of a larger project.
I hate to add to idle speculation, but it sounds like the only kind of project that might be acceptable would be if an experienced developer independently proposed to write a relatively small, and standalone component such as a desktop accessory, small utility, or simple device driver.
A "piece" of a larger library or component would not be acceptable. Maintenance on existing libraries would not be acceptable. In the case of ReactOS related software, the end result in its entirety should probably be usable under Windows XP/2003.
The creator/developer would have to comfortably say that they could complete it by X date or using Y hours. And they would be held directly responsible for delivering on time.
So the vast majority of the type of work ReactOS really needs wouldn't fit in this.
It's a little vague how much detail they want in a specification document. Sometimes these can take as long to write as writing the software itself.