Great questions and thanks for starting off the thread! 
First off, please do send folks with profiles problems to Bugzilla (or file bugs for them, if they aren’t able or interested in filing a bug). We triage the bugs regularly, and it’s important for us to keep track of how many users are reporting problems so that we can look for trends. Some issues may be duplicates of known weirdness bugs collected under the metabug https://bugzilla.mozilla.org/show_bug.cgi?id=1991913.
Also, to address your 2 questions in reverse order 
- Are there people willing to investigate such reports at all?
Yes! We (engineers who worked on profiles) continue to triage bugs as they come in, and we are continuing to do work to improve the system as time allows (we’re all staffed on other things but have some time allotted for maintenance work).
- Is there a way to understand what happened in the cases of data corruption, for example?
Yes, it depends on what exactly the user has been doing prior to apparent data loss.
It is important to clarify that profile data is almost never lost, as in destroyed. What tends to get broken is the connection between the user’s profile and its entry in profiles.ini, which we use to find the profile at startup.
Now, to answer your other questions:
If I create profiles from many different profiles (and different types of profiles), is there a chance to break Firefox that way?
I know there are safeguards for concurrent profile management, but is there a possibility that one of the profiles will pick up a wrong database / create a new one?
Also, just out of curiosity. I haven’t really dig into that, but from what I understand, the only difference between legacy and selectable profiles are colors/icons (which prevents us from using the legacy profile type, because there’s no place for those fields). Is that understanding wrong? You mentioned concurrency on Reddit, but didn’t we have that for legacy profiles already?
I’ll have to explain the profile system in a bit more detail. (Note: I started on a comment but it pretty quickly ran past 1000 words, which seems long for a discourse comment, so I’m going to turn it into a blog post and link to it here instead.)