While something like your idea has been a feature request, it may not have seen much demand because people have been able to use the existing features for their specific purposes. You can already have user shares that remain on cache, and you can have redundancy of the cache pool. Normal HDD read speed in unRAID is just that, only write speed is affected by parity. And normal HDD read speed is usually enough for 1GB ethernet.
For example, I have several user shares that stay on cache (cache-only or prefer). All my other user shares don't use cache for speeding up writes (cache-no). These all write directly to the array because they are mostly unattended downloads and backups, so write speed is unimportant.
My user shares that remain on cache are for applications such as dockers, but I also have files that are accessed frequently (music for network players and pictures for screensavers). I keep these on SSD cache so no HDDs have to spin up. And my DVR recording goes here also since I may or may not want to keep these and I can write them while reading others that have already been recorded.
And there is the ability to mount drives (and network shares) outside the array. I mostly use this feature for creating backups that I keep offsite, but it is also handy for copying files from other sources.
Of course others will have different ways they use these built-in features.