The personal preference settings are a different thing. When you switch a prime 4 on, it doesn’t matter if it takes 10 milliseconds or 10 seconds to load your personal preferences. But only RAM type memory can “promise” to play back a sample instantly when you press a button. If the sample is on hard drive or even SSD there’s going to be a delay, some latency if you like, between when you press the button to fire the sample, and when the sample is ready to fire.
The primes load a full track into RAM memory yes, but only that track you’re playing on that deck right then. So firing a “It’s time” or “this stuff is really freasssh” sample clip from a different sound file via “sample pads” over the top of a different song isn’t going to work, not all on one deck / one layer anyway. You could use a different deck or a different layer, but you can do that anyway already.
Sampler functions need RAM which isn’t already in use for the currently loaded track.
I suppose you could have a situation like some denon CD players used to have, where you decide beforehand whether to you to sacrifice some features in favour of other features. Like on the alpha track feature on the dnd9000 and the Dns5000. On those you could have two layers with two hot starts per layer, or you could have 4 hot starts if you sacrificed a layer. But would you really want to be in a situation where you press a button to do something and a message pops on screen saying “you can’t do that right now because the x feature is selected” or “Layer B not available while samples are loaded”
Some will be ok with that, some won’t, I spose