linux_admin’s purpose is to essentially be a wrapper around shelling out, so that CLIs can be accessed in a simpler, object oriented way. Additionally, linux_admin is used for parsing stdout from those CLIs to keep the parsing logic can live in one place.
To the purposes of your proposal, I can see linux_admin also being used to look at filesystem layout, and then extrapolating information from that. For example, I’ve thought about moving some of our lib/util/miq-system and lib/util/miq-process code into linux_admin, which wraps ps and also looks at /dev/proc , but as Rich said this requires executing in the running VM context.
If Rich’s virtual file system proposal were implemented, then we could execute against a non-running VM context, but only filesystem based pieces would work. However I think that proposal is some time away.
The only way I can see this working in the short term is if you made a method in linux_admin that accepted the filesystem content from an external source. linux_admin itself could leverage this method for the running VM context, and fleecing could use it after it retrieves the data.