i agree something like that would be nice, but there are also quite some problems that can occur.
for example most of my configs contain sub configs for better inventory management, if a user with close to no xim background knowledge copies that config he/she might forget to adjust the activation keys in the sub config.
there would need to be a mechanism that makes the user aware of something like that, and even then that wouldnt be enough as most people would probably close such a pop-up without reading it.
another problem are firmware compatibility issues, if a config is created with the latest beta firmware then a user with an older firmware couldnt paste that config into their xim.
visiblity would also be a thing, a database like that could soon have several thousand configs since a lot of people might just want to add their own config to share them with friends via that service, and then it will start to become quite difficult to find the good configs in there. new configs that may be really good might just vanish in the flood of other new configs.
i like the idea but there are a lot of problems to solve when doing soemthing like that

.