It took a while and a few back-and-forth shipments and no doubt lots of work for Aram, but now he has adapted the BikeOn motor kit so that it also works for bikes like mine. Many thanks, Aram!
My bike has an 11 speed Shimano mountain bike cassette and cassette hub and a chain stay with derailleur cable boss right where the previous BikeOn version would have wanted its torque bracket. This Shimano cassette hub is 1.8mm shorter than the road hub, and therefore has smaller clearance for the BikeOn motor between wheel and chain stay.
Both of these issues needed adaptations on the BikeOn side.
On the bike side no extra parts or adjustments are required, the kit has good clearance to the spokes without any changes or spacers added to the cassette, the derailleur cable moves freely, and 7 of the 11 cassette sprockets are useable. The derailleur comes to a safe stop against a fixed (non-rotating) part of the BikeOn kit, and there is sufficient clearance of the chain to the BikeOn front baseplate.
The torque sensor can be height adjusted to allow for different chain stay and motor torque bracket (the part below the chain stay) heights.
I did a 30 mile test ride with an almost-final version, including a 2.8 mile uphill section with 5.2% average grade (Turnbull Canyon near Whittier, CA), and the unit meets all my requirements. I can easily go 20 mph on flat ground (actually 22 mph at 20% motor support level, and 25 mph at 45% motor support level) at my normal exercise level of pedaling (~100W human power, I'm estimating), the unit supports continuous uphill riding at a good speed (9 mph up a 5.2% grade) and most important, cadence (70-80 pedal rpm). This takes the larger lowest gear due to the lost sprockets into account. The motor doesn't overheat; for most of the uphill test it was actually smoothly regulating at its thermal limit, and when pushing it like on this test uses about 10-12 Wh/mile. I used about 1/2 of the capacity of the smaller of my two 48V batteries, discharging the 15Ah unit from 54.5V to 48.5V, which agrees pretty closely with the energy input recorded by the BikeOn unit.
The 30 mile ride ended when I accidentally kicked the battery cable from the motor while pedaling (I had routed it in a 180 degree-turn right at the motor, which probably left a bit too much tension on the connection), and blew the fuse and possibly also the FETs (still waiting for Aram to confirm). Dismounting the unit and pedaling home the remaining ten or so miles worked just fine. Apparently disconnecting the cable from the motor while the motor is running is a no-no.
Below I'm including some plots of power and energy used and of speed vs time. I'm still working on converting the torque sensor reading to something more closely related to pedaling torque. One can nicely see the near constant power output and speed while on the 2.8 mile climb between 12:14pm and 12:37pm, interrupted by a five minute break, and the two occasions where I used the motor at 60% support level for a short time until it started to reduce power to keep the temperature under control. Ambient temperature was in the high 80s, if I remember correctly.
Motor output for the climb is about 130W for the constant part, and my output was about the same, and about the maximum I can do (pulse rate close to 170, which is a good rate for somebody ten years younger than me...

I believe speed is km/h, but I noticed the BikeOn calibration was maybe 10 or 15% off (low); for the constant speed part of the climb the actual speed was about 9 mph or 14.5 km/h.
I was actually surprised when I first saw the data that I had pulled up to 500W out of the unit. But for 25 mph on the slight grades leading up to Whittier that actually makes sense. Having the motor support makes it very tempting to go faster, even uphill. All in all I believe I got a better exercise with the motor than on the same tour without.
The jump in the blue curve (Wh) actually indicates some missing data between 11:30am and 11:50am. The horizontal time scale is not necessarily linear.
