It's an interesting idea, but I would strongly suggest being careful about offering active tests and procedures. The ABS bleeding as an example is possible if you're careful and understand the limitations with certain ELM327 clones or better yet an OBDLink or good J2534 device, but even if the procedure is coded correctly, something like Bluetooth has the risk of being disconnected, or if it's not a real J2534 setup you can have serious problems with timing or just getting a processor wedged. I could see an ABS module getting stuck open and broken this way, or some of the tests you could do in Techstream or Tech2 can legitimately damage a power train if you don't understand what you're doing. Programming via anything short of a real J2534 is also a siren song, as it's technically feasible theoretically even with something like a CANable or OBDlink MX+, but again timing, buffer sizes, and generally needing to provide external power basically anytime you need to do something like program (and that's not obvious if someone hasn't told you or you haven't bricked an ECM), would make me really hesitant to hand that gun to just anyone.
In thinking about it, someone is also likely to ask how you figured out how to do an active procedure like an ABS bleed. Maybe you sniffed an Autel or a Modus, but I wouldn't be surprised if certain manufacturers got up your ass very quickly about the provenence of your code. If you're in China like Autel was when they first built their tools, I guess you can ignore manufacturers being upset about the lost revenue stream, but otherwise I might be concerned.
On a related topic, is there a place i can follow you (like on twitter etc).
Fair points. Yes active comm needs a lot more testing & is fairly risky, so there needs to be very good guardrails (exact model matching for a given command etc), together with solid communication. I think bluetooth is much more reliable today than it used to be, but I wouldn't use a cheap elm device with this for sure.