Jim beat me to it. I'll add this anyway.
Yes, you can run as many local libraries as you want on a MC installation, and switch between them as desired. I do that for some of my testing.
Also, when you connect you Workstation to your Server, a copy of the Server Library is transferred to the Workstation. You can create and edit Views on the copy of the Library and they will never be synchronised back to the Server. Other changes, particularly all Tags and Playlists, will be synchronised back to the Server. When you close the MC Client on the Workstation and then reopen it, a fresh copy of the Server Library is copied to the Client. So all your experimental Views will be wiped out.
I use this all the time to test Views against my Server Library contents, without the risk of messing up existing Views. If you created a View you like, then you could save that View, transfer the file it creates to the Server, and then Load that View into the Server Library.
The Rename, Move, & Copy Files function does not work on a MC Client, so no files will get mangled.
Testing video files on the Workstation is a bit of a different issue. You could just import them into a local Library, or you could open the video with the Client without importing it, since you can't import into the Server Library from the Client, or the copy of the Server Library that is being used on the Client. But you can use the Windows Shell Integration features to play a video, and hence test them, if that is what you want.
So, most of what you ask makes sense and is doable, even using a Client connected to the Server Library. Some of it may not be, depending what the "other information" you want to test is. In that case, use a local Library.
Of course, you can always back up the MC Libraries if in doubt, and Restore it if you don't like what happens.