In addition to standalone recordings taking a lot of network traffic to load per-track, and loading extremely slowly... after the standalone recordings have been loaded into Picard, it is extremely slow to try to delete or reset values on a set of standalone recordings.  Using 100 standalone recordings and then trying to preserve original values on most of the fields except a couple, Picard stops responding to user input, maxes out around 10.3% CPU usage on a Core i7-10700 (16 logical processors) and probably takes somewhere between 5-20 minutes before the operation completes and the user interface responds again.