Hi Christopher,
I think you have quite a task on you hands there, I was struggling to made sense of the MIDI implementation charts. Not that I am much of an expert.
I have attached a text file with a excerpt from the page on the link below:
http://www.gmarts.org/data/jv-midiman.htm
I think the data you require is in here, under the address column. The bytes are listed as hexadecimal, so you will need to convert the Hex to Decimal using the Ctrlr MIDI calculator (A0 = 10, on the tenth line no less! 0B =11 and so on). The Controller values are at the end of the line.
Use the Ctrlr MIDI Monitor to grab the data from a Sysex Tone Edit Dump and interrogate it byte by byte. Use one patch as a reference and stick to it, as you say tweak a parameter and see where it changes. I printed a copy and then wrote notes on it as I went. I also copied the data I grabbed in to a text editor and using a mono spaced font such as Courier I compared it line for line.
I think the actual data you require will start on the ninth or tenth byte after all the Sysex IDs and stuff. See below:
status data byte status
F0H, 41H, dev, 6AH, 12H, aaH, bbH, ccH, ddH, eeH, … ffH, sum F7H
Byte Remarks
F0H = Exclusive status
41H = ID number (Roland)
dev = device ID (dev: 10H)
6AH = model ID (JV-1010)
12H = command ID (DT1)
aaH = address MSB
bbH = address
ccH = address
ddH = address LSB
eeH = data : The actual data to be transmitted.
Multi-byte data is transmitted in the address order.
ffH = data
sum = checksum
F7H = EOX (End Of Exclusive)
Here is some noise I organised into an acceptable format:
https://soundcloud.com/lfo2vco/a-dark-crystal