Hello Fuzzlix !
Nice ideas, really. I hope you could get help from users. As we said, we try to keep some Storm's specificities, but we could contribute also if we see a real dynamic around a community database.
Of course, all code side is ok for us. I suggest you to have a deep look in DOLDatabase project, which is an handmade ORM.
There are plans to replace it by other things (mainly Linq based provider), but a 3rd party ORM could also fit. The main goal is a real data access layer, with no specific database need. I accept all linq compliant and open source technos, if someone is ok to dive into it
(NHibernate, EntityFramework, DB4O...)
This said, let me explain you a bit. Our custom ORM defines data-related stuff: table creation, table modification, pkey and indexes implementation, foreign keys, datatype, null values... You can have an example in the various tables/.cs files into DOLDatabase. Notice this is not entities, a class is the exact table representation.
The main work is to revamp the table attributes, in introducing missing constraints (in example, iirc, there are no FK in quests, but all quests are rattached to a character. Deleting a char must delete the quests).
For your kits, i guess you can rely on the numerous package_id fields. I don't think they 'll be enough to handle dependencies - imho you'll have to think about a protocol.
I also guess we could see for a database server accessible for you.