Just did that. I'll keep you informed.
The thing is that I did not register a product, since I don't own any yet. That's why I couldn't check whether the bug also occurs when syncing or if it's a file storage thing only. I saw the "Line6 Edit" software as a great possibility to "get my hands on", check out all the different parameters and routing capabilities, so I could see what the device is capable of, before actually acquiring the product. However, after I found this bug (which was soon enough ;-) ), being a software developer myself, I thought I somehow had to report this so it can get sorted out. (It's probably pretty easy to fix.) I don't know how "seriously" the support tickets of "non-customers" are taken though. I mean I didn't pay anything (yet), so I guess I'm not entitled to get any kind of "support" (yet). It's not a request for actual "support" though, you see? What I'd like to do is "file a bug report". However, like most companies, Line6 doesn't have a public bug tracker (yet). ;-)
I would have gone even more in-depth and checked whether the parameters are not saved correctly or not restored correctly. However, the file format that Line6 uses unfortunately is binary, proprietary and undocumented (and probably related to the way the patches are stored inside the memory of the actual DSP?) so I cannot actually tell what's in the file.