Sorry for the delay.
Thanks for all the details you posted here.
Worksessions or RWS files do not save layer visibility per detail.
However, both Rhino 5 & 6 will save per detail layer visibility of the active file only.
This is the same information that any Rhino files would normally save, even if Worksessions are not in use.
If you turn off a layer per detail, that is part of the active file, or hide objects in the detail that are part of the active file, and save the file, this will be saved or restored upon reopen.
If you turn off a layer per detail, that is part of a non-active file, or hide objects in the detail that are part of the non-active file, this will not be saved or restored upon reopen. Hope this helps clarify and illustrates the difference.
To be fair, this is confusing because Rhino does hide the layer and objects in the non-active file “temporarily.” It just does not remember it. If saving the visibility of non-active does not fit the logic of the worksession RWS file, then Rhino should not temporarily hide them either, in my opinion. So, I really believe that is the bug. And the first item here is a wish or feature request.
The Help file does say that LayerStates of the worksession file are saved. This is true, but only of the visibility state of the parent layer, not the nested layers. So if you have a LayerState with the LayerState manager, you can restore the layer state from the LayerState manger, and the visibility of the parent layer will be restored. Again to qualify this, no changes to the settings on the nested or child layers are stored or restored in the LayerState.
Thanks for the bugs and wishes, getting them posted now.
Mary Ann Fugier
McNeel Technical Support and Training