No, completely the opposite, I expect the regular user to not be able to do most of what I outlined. I'm not saying the easy button feature isn't needed, I'm pointing out that a linux savvy programmer COULD give us a plugin to handle it, but that fact that none have is evidence that if it's going to happen, it's probably going to have to wait in line with the myriad of other features that users are asking limetech itself to integrate.
Hopefully the recent paid staff additions will accelerate the implementation of these many wanted features, but I'm not holding my breath.
A great many (almost all?) of the features currently being added to the core of unraid started life as user created add ons, and have been slowly incorporated. The fact that nobody has stepped up and written a community supported plugin to do this specific function says something. I was simply pointing out what obstacles are there for a community member to set this up. Doesn't mean it won't eventually happen.
Who knows, maybe limetech has this all lined up for the next major beta after the 6.9 series.
I've also left out some major issues that would have to be addressed with a slot removal function, namely the difficulties posed by the very thing that makes unraid different. Each drive slot is an independent file system, and can be referenced with individual specificity if desired. That means that if you remove a slot and there are still file paths configured to write to it directly, bad things will happen. There are so many different places that could be done, it's difficult to cover your bases, as simply moving the files to a different path doesn't mean the application that wrote them there will be able to find them at the new location. If everyone was forced to use fuse /mnt/user paths, there would be less of an issue, but that's not how things are right now. /mnt/diskX is a perfectly valid path to save and retrieve files, and some people use direct paths for practically everything for speed and organizational reasons. Also, the /mnt/user shares have include and exclude rules that reference the disk slots, you have to reconcile what happens when one of those slots is gone, and how to allocate the data that is to be moved from the slot to be vacated.
It's not as cut and dried as it seems.