Hi, i‘m nur 100% sure if I understand you correctly since English isn’t my native language.
The wavetables have all the exact same size, independent of the complexity. I guess that the interpolation is done by the wavetable editors engine. But if i remember correctly, i read in the manual that the Blofeld calculates the intersection between every step: the Wavetables consists of 64 steps and the Blofeld has 128 „steps“ (0-127), so if you go from wave 1 to wave 2 there is a pseudo step between, in order to make the transition smoother. If a complete wavetable is finished in the editor, it can be saved as sysex file. Those can be uploaded with a sysex manager. The name and the position for the table is written into the sysex file of the wavetable. What’s kind of strangethat the size of a WT set is really small, but i don’t believe that Blo is fast enough to do the whole interpolation in real time, but maybe it would be possible that the Blofeld calculates everything after the import and saves then a complete caluculated version of the set, but personally i believe this is completely done by the wavetable editor.
I have the patchbase editor for the iPad, it supports a lot of different synths (even Volca FM and a lot of classic we’ll know synths). But i program my patches direct on the hardware, if you use it often, you know exactly what’s the quickest way to change and set things up. I use it as memory training 
But usually editing via sysex can be slow. When i use a Volca fm and the app, the data are send over a midi interface(slow Transfer Speed) . If everything is set up perfect, it is faster but not fast enough to modulate a patch in real-time without delay.
For which synth did you write your Wavetable editor? I don’t know Max. Is it some kind of software devolpment kit that can be integrated/wrapped as plugin for Ableton?
When I create a wavetable with the editor, i usually create a waveform for the first step, and for the steps 16, 32,48 and 64. I then use a integrated morphing algorithm that calculates all the steps between. The only problem is that the editor can’t play the waveforms as audio, so I have to upload them into the Blofeld to listen how the sound.
I used the „WALDORF BLOFELD WAVETABLE CREATOR“ app. The editor „Audioterm“ application can play the audio that results from the wavetable, but I have to read the manual first since it’s a little more complex. Both apps can theoretically load short „wav“ files to resynthesize/extract the waveforms and make a table out of it, but i haven’t tried this out (maybe tomorrow).
But what’s strange that even a complex Wavetable consists of only a few rows of hexadecimal code, but all the Wavetables have the same size. But it looks like everything is done by the editor itself…
and I did ordered a small amp. The Roland Micro Cube, can be used with batteries and has multiple inputs. This makes it perfect for summer, to go out in nature and play beautiful pad sounds!
for performance and sequencing the blofeld. Very occasionally I will supplement an LFO from Octatrack, but usually that is only when I don’t want to change the patch on the blofeld. That said, the two are a killer combo. Really really fun.