I didn't want to work on something that's already been done, but it seems like a fun project. 

1. Figure out what makes up the tone section,

2. Write something that strips out the tone info and saves it as a small, easily shared file. 

3. Write something that adds the tone info from step to a blank .JAM file. 

Then someone just needs to get the file from step 2 and run the utility from step 3, load the .JAM file and let the Spider Jam get its tone from there.

This beta release then gets debugged etc.

Then go through the steps you outlined to figure out what hex value controls what tone.  And finally write a utility that prints out the results.  This is the production release.

OR, Line6 could just tell us what the format is.  Too much to ask?

This ended up being too hard for me.  It was fun looking at hex again--for about 20 minutes.  It would be nice if Line6 simply released the info by filling in the blanks in the attached document.