Well...I'm closer. I think.
Pulled the latest changes from Peabody (looks like it may be using chibios now?) and reflashed (with the same make a .hex and flash it with the cleanflight chrome tool letting it fail once goofiness that my board seems to insist upon) everything seems configured right and the matching GCS all seems to work.
I still get a uavobjects mismatch error - which seems to be because I'm not getting a version from the board. Not sure what's going on there. I had this same issue with the other builds I've tried as well - they give me the same blank for uavobjects version causing a mismatch with any version of GCS.
And even odder...my board is acting super goofy. I flashed it back to cleanflight and confirmed it's doing the same goofiness there as well now...and it wasn't before but this seems hardware related. Specifically if I power it off a lipo I get a solid blue light and nothing else. But if I power it off USB it works as expected...except the power pin on the main RX connector only shows 2.5v now.
I'm also unable to get the motors to spin up - or even get anything out of the ESC's with Tau. With CF I can get the motors to respond normally. But with Tau I get nothing even after confirming they're set to PWM with 400hz updates. These are just emax ESC's on here with no oneshot. I see that Groucho/acceleroto is using oneshot but I'm kind of wondering if maybe normal PWM output isn't working since I haven't seen anyone else report it is yet.
Hope Sparky2's are available soon. Getting sick of fighting with this Naze board and found a neat new place today that I'm dying to fly this little guy