The binary strings inside the <bin name="audioComponent"> … </bin> element inside every /…/<obj class="MInstrumentTrack" …>/<member name="DeviceAttributes">/<member name="Synth Slot">/<member name="Plugin"> are simple hex dumps, 2 digits 0…9A…F per byte, chopped 64 characters (32 bytes) per line except the last, possibly shorter one. The format clearly depends on a particular VSTi instrument.
I. The SINE Player, that @Sebastian_Alvarez mentioned, at the line 163974
<string name="Original Plugin Name" value="SINE Player" wide="true"/>
has almost all of its data in a UTF-8 JSON string, save for a few binary leading and trailing lines:
SINE Player JSON data
{
"fileFormatVersion": "1.0",
"samplerVersion": "1.2.2",
"instanceName": "SINE Player",
"dynamicXFadeCC": "11",
"velCCXFade": "1",
"disableExpressionCC": "false",
"masterTune": "440",
"masterTempo": "120",
"syncToHost": "true",
"keyswitchOptions": {
"ksAreaStartHighInstrument": "24",
"ksAreaStartLowInstrument": "96",
"ksAltRelease": "23",
"ksAutoSustainMute": "21"
},
"selectedEntry": {
"instrumentIndex": "0",
"articulationIndex": "0"
},
"renderer": {
"prefetchPageCount": "256",
"latencyBufferCount": "1",
"readerCachePageCount": "1024",
"readerCachePageSize": "4096",
"sampleCachePageCount": "32768",
"controllerMappingRules": [{
"inController": "1",
"outController": "1",
"useCustomCurve": "true",
"curve": ["0", "1", "2", "3", "4", ...[SNIP]..., "104", "105", "106", "107", "108", "109", "110", "111", "112", "113", "114", "115", "116", "117", "118", "119", "120", "121", "122", "123", "124", "125", "126", "127"]
},
...[SNIP]...
]
},
"preloader": {
"preloadTime": "0.25",
"lockPreloadedPages": "true"
},
"instruments": [
{
"instanceId": "54881345-eb61-4d43-b360-e87054ba3c17",
"id": "1996",
"title": "Violins I tutti",
"midiChannel": "1",
"omniMode": "false",
"performanceType": "default",
"performanceScript": "",
"keyRangeLow": "55",
"keyRangeHigh": "100",
"transposition": "0",
"volume": "0",
"mute": "false",
"mutedbysolo": "false",
"solo": "false",
"switchMode": "MONO",
"switchType": "KEYSWITCH",
"polyMapPerformanceMode": "SWITCH",
"polyMapTrackingType": "CC",
"variationCC": "3",
"color": "50",
"ksshift": "0",
"syncToHost": "false",
"lockToBeat": "false",
"autoTempo": "false",
"multiplier": "1",
"arrangerActiveState": "true",
"arrangerLeadVoiceState": "false",
"arrangerBassVoiceState": "false",
"arrangerVoiceSettingsModified": "false",
"arrangerLeadVoiceRangeSettings": "2",
"arrangerBassVoiceRangeSettings": "0",
"arrangerRetriggerActive": "true",
"micPositions": [ ...[SNIP]... ],
"articulations": [ ...[SNIP]...]
}
]
}
instruments[0].title = "Violins I tutti" is an easy guess. 
II. Here’s another VSTi species, line 55992:
<string name="Plugin Name" value="Opus" wide="true"/>
whose dumped state is just over 100000 lines of binary data (about 320K) long, but near the end contains the following JSON snippet at lines 159394‒159476 (three dots in strings are bytes encoding one character in UTF8; this is an artifact of my doing a byte-level dump):
Opus JSON data
{
"bounds": {
"width": 1146,
"height": 770
},
"inspector": false,
"inspectorTab": 0,
"instruments": true,
"keyboard": false,
"workspace": {
"Browser": {
"browserTab": "library",
"tagBrowser": {
"tags": [{
"class": 1,
"lastSelected": 0
}, {
"class": 2,
"lastSelected": 0
}, {
"class": 5,
"lastSelected": 0
}, {
"class": 6,
"lastSelected": 0
}, {
"class": 3,
"lastSelected": 0
}, {
"class": 4,
"lastSelected": 0
}
],
"instrument": {
"class": "InstrumentInfo",
"title": "09-Celeste",
"fileName": "09-Celeste.ewi",
"entity": 10659,
"path": "GM Bank/009-16 CROMPERC",
"installationState": 0,
"description": "GM BANK ... This is the world...s first 14 GB General MIDI bank. Most (but not all) of these programs can also be found in other folders in this library. The GM bank is mostly for convenience and to adhere to a standard.",
"instrument": "",
"keyRange": "",
"loadSize": "",
"keyMin": 36,
"keyMax": 96,
"size": 0,
"productId": "com.eastwest.11",
"productEntity": 0,
"productTitle": "EW Goliath",
"rating": 0,
"comment": ""
},
"playPreview": true,
"previewGain": 0.16295507550239564
},
"diskBrowser": {
"product": "com.eastwest.8010",
"instrument": {
"class": "InstrumentInfo",
"title": "18V KS Master",
"fileName": "18V KS Master.oib",
"entity": 18853,
"path": "18 Violins/05 Keyswitch",
"installationState": 2,
"description": "Keyswitch (KS) Master instruments can switch between many individual instruments or articulations by playing their respective blue-colored keys (...keyswitches...) on the virtual keyboard. When an instrument or articulation is actively selected, its corresponding keyswitch will be highlighted in yellow. This is one of the fastest ways to cycle between articulations in real time, and it makes it easy for you to drop notes into the piano roll and switch articulations after the performance.",
"instrument": "",
"keyRange": "",
"loadSize": "",
"keyMin": 0,
"keyMax": 0,
"size": 0,
"productId": "com.eastwest.8010",
"productEntity": 0,
"productTitle": "EW Hollywood Strings Opus Edition",
"rating": 0,
"comment": ""
},
"folder": [{
"path": "/Users/Shared/Eastwest/EW Hollywood Strings Diamond/Hollywood Strings Opus Instruments",
"selectedItem": 0
}, {
"path": "/Users/Shared/Eastwest/EW Hollywood Strings Diamond/Hollywood Strings Opus Instruments/18 Violins",
"selectedItem": 4
}, {
"path": "/Users/Shared/Eastwest/EW Hollywood Strings Diamond/Hollywood Strings Opus Instruments/18 Violins/05 Keyswitch",
"selectedItem": -1
}
],
"selectedPath": "/Users/Shared/Eastwest/EW Hollywood Strings Diamond/Hollywood Strings Opus Instruments/18 Violins/05 Keyswitch",
"playPreview": true,
"previewGain": 0.16295507550239564
}
},
"Mixer": null,
"Performance": null,
"Player": null,
"selectedPage": "Player"
},
"instrumentsCollapsed": false,
"project": {
"location": "/Users/sebastian/Documents"
}
}
Is this enough to determine the patch loaded into the sampler? There is a mismatch between instrument and diskBrowser.instrument. I may have missed more JSON-formatted pieces in these 100000+ lines, of course.
Both VSTi’s are apparently built with JUCE, as its name occurs at the end of the binary dump, so their binary dump format is probably documented.
III. But Kontakt 7’s binary dump data, line 2628,
<string name="Plugin Name" value="Kontakt 7" wide="true"/>
look totally opaque to me; nothing like readable strings there, unless I missed them. Of course, the data may contain opaque binary library and instrument IDs only, as Kontakt has its own ecosystem.
It looks like some library and instrument names can be recovered with a little effort, but not all can be.