In fact, make sense if you understand how the profiles are implemented.
The GlobalVariable compiled class which is generated at runtime in the compile phase it is scoped to the suite.
Which means, once the suite ends (no matter if it was started in a collection or standalone) the instance of the generated GlobalVariable class it is destroyed, during the run of the 2nd suite (no matter if it is running sequential or parallel) a new instance for the running thread is created based on the values defined in the selected .xml file (the profile)
So, on short, it is not possible to re-use values set in the selected profile during a suite run for another suite run, even if the selected profile is same (and honestly i see no reason for such feature … but this is just my opinion)
To achieve such goal, you may want to export the needed variables to an external file or a third party db (postgres, mysql, sqlite, whatever) and reuse-them by implementing a custom keyword.
Or … find a way to modify the profile .xml during the execution of the suite.
But pay attention, if you attempt to run the suites in parallel, lot of bad things can happen. And i doubt will work even with sequential execution too … feel free to try.