I dunno. If one takes a simple approach it might be do-able. In the case of Cura, it just drops at the end of the file what is a big JSON object which is then chopped up to control the line length. It's well-marked with a comment so it would be easy to find and grab.
It might be simple enough to then just have this text available for a hover-over popup to display what it found.
Rather than reading all the files, only reading the selected file would again simplify matters. A single line (or FontAwesome icon) added to the State side panel widget would be the point to query. Hover over this and a popup box would display what was found.
Personally, I'd rather have an ugly report than to wonder which slicing decisions I made for this file.
That said, I actually have written a Go language CLI which will report some Cura-specific information which was important to me at the time. In theory, one could compile it for the Raspbian operating system, place the executable into the
~/scripts folder, call it from Python using a simply plugin approach.
Slicer: Cura_SteamEngine 2.3.1
Profile: Low Quality Robo C2
Filament size: 1.75
Hotend temp: 190
Bed temp: 0
Speed 1st layer: 10
Print speed: 50
Travel speed: 80
Infill pattern: cubic