From other recent posts... I suspect he's looking to somehow hack any files on disk related to toolbar and perhaps lister "State Data" to try and come up with a way of launching listers with specific toolbars opened for specific workflows and use-cases where he wants something other than global default toolbars switched on.
Leo's questions are all still valid to give you a definitive answer towards whatever you're trying to do... But if I've guessed the intent correctly - I think you're sort of hung for a way to hack your idea together. I say this assuming that to do what you want, the thing you'd need to work with would still be "local" toolbars as in the referenced thread... That said, there's certainly disk files that store lister layout data, whether it be the default lister, a saved layout, or that other last bit that Leo asked about (listers that were open when...) as well as a file (toolbars.oxc) that stores the "global" toolbar on/off state... But I don't think there's any disk file that persistently stores anything related to "local" toolbars (which are the only toobars associated in any way with a "specific" lister) which makes sense if you consider that such info isn't relevant for anything other than a lister that's already open where you've turned a toolbar on locally. That sort of lister ~state info~ is probably just kept in memory for that specific lister - unlike the "global" toolbar state info which would need to persist somewhere so that Opus would know (for instance) what toolbars to flip on when launching a lister after a reboot... etc.