That process sounds intimidating and it would probably be challenging enough for me to worry about doing. I think I'd rather not do it just so that problems that my bike ends up having are things I can fix on my own. Learning how those motors work and learning to troubleshoot their problems doesn't seem to be outside of the realm of possibility though.
"those motors", if you mean the type you're talking about using two of that would have to be locked together to use with one controlller, are just the same kind you're already using, if you are using BLDC 3 phase motors like the typical RC motor.
Brushed motors are very very simple to use, and dont' even require a controller if you have a switch big enough to handle the spark/etc from engaging under load and you don't need variable control over them.

But the controller itself is also much simpler than a BLDC (brushless DC) controller (which you're already using iwth typical RC motors)
I'm on an FRC robotics team we work with entry level robotics equipment meant specifically for FRC.
That sounds like a challenge.
We get most of our spur gears from West Coast Products and our planetary gearboxes from Rev which also make the motors we use. Some of these motors are terrifying! We use Kraken x60s and they are hardly larger than the hobby rc motor that I mentioned above, but they're rated for 360a and can put out 7nm of torque. That along with the fact that the ESC is built in and they have very accurate continiuous encoders means they're very capable, and very expensive. They could be worth it to be if I could know for sure that I could keep it cool.
The Kraken x60 looks interesting, is apparently a low-kV low-rpm type of motor from the first couple results on a web search, which is why it takes such a high current, all relative to the typical RC motors that have a high kV and use thousands of RPM to get the power output they do. So they'll be quieter just because they are not spinning as fast, even if they are still using gearboxes (of which I saw several types specifically made for them, including some that drive small (aimable with a separate servo motor?) caster wheels).
Without experience with those motors, or a dyno chart, I'd guess that they are not rated to take that 360A continuously without significant external cooling; they're just too physically small.
I would guess that they are probably better suited to drive a ground vehicle than the higher RPM types, but you'd probably still have to run an external cooling system.
Additionally, wiht a built in controller, you have *two* sources of heat within a small space; in many applications this isn't an issue but any application with high continous power usage means more heat build up more rapidly in a smaller space, so they usually require significant external cooling.
If they're using continuous encoders (like SIN/COS) that makes them much more useful for positional control, exact movements, etc., and can make them easier to control in any other application (some of the BLDC powerchair motors also use SIN/COS). But few controllers can read those types of encoders (almost all of them are either sensorless or UVW-ABC hall sensor type).
As for keeping it cool, you can find out what it would take to do that by testing temperatures of the ones you have access to under known loading conditions, and extrapolate from a series of those conditions and measurements what it would take to keep one cool under your loading conditions.