Software is allowed and I'd definitely support a project that hits on at least some of what I described above.
I did look into this slightly more and the impression I got was that software projects are not encouraged under Kickstarter, but that Indiegogo is more flexible.
On the software front, someone has to get the ball rolling by writing a reasonably detailed draft specification for the software. Until this is done and also until debated, modified and finally agreed by some core project team then I'm not sure how it's going to progress.
For instance I can see a lot of potential debate between those who'd prefer a fully local solution and those who would rather have everything possible in the cloud (not that the two are totally exclusive but trying to ride more than one horse to start with will be tricky). And another battlefront will be between those in the simple, clean, 'less is more' camp (count me in) and those who press for more and more readings of every conceivable kind to be included (resulting in what to me is the bane of a lot of wx software - just too much information crammed into the display space ( typically far to much for the layman to take in at a glance) and often not very elegantly presented).
Another major question is how units should be handled - personally I'd stick with just one system of units throughout until the final display stage when appoprriate conversions can be made.
And one other difficulty is how to actually recruit coders to the project with good technical skills in the various required areas.
One way forwards might be to break the project down into separate functional areas, with agreed interfaces between them. My picture has always been:
1. Data acquisition + initial processing/summary (definitely Pi territory)
2. Uploads of real-time data to eg an MQTT broker in an agreed extensible format eg JSON-based (Pi)
3. Long-term storage on a reliable platform (probably not Pi because of the lack of robust memory - better suited to cloud)
4. Real-time browser-based front-end receiving MQTT messages pushed from the broker
5. Additional functionality in the browser-based front-end to provide reporting and retrospective charting via queries (probably via websockets) to the cloud database.
We can debate the details, but the point is to break things into more manageable chunks with agreed interfaces between them.