[Read Desc] Why motor has to be over a control box?!, sdac?

I am not a person who usually does expressing complains. But you guys who build things using something like advanced motors, knows how tedious it was to set this up.
Now look. We have 2 of these motors. Left is simple and right is advanced DC motor.
The question is, why the advanced one need this interface box?
In real life, it is for basically, to operate it. By how?
Some motor requires even more complex procedures as a drawback behind those advantages above usual motor, such as to grasp the shaft to magnet A, then magnet B, then Magnet C, back again and repeat.
Why has to be like that?
Because that motor is brushless. Of course, everything is brushed digitally using transistors as you can see on our PC fan e.g.

Why I mostly saw only 2 leads on my PC fan?
That's because its digital brush (factors the speed) has been fixed.

I have my fan has more than 2 leads!
That mean your fan speed can be tuned to be slow or fast based on something.

Back to topic!!!

Is there is any simpler way without making a hassle, and decrease space usage?

I mean to have a motor that has 3 input:
- Power
- Speed
- Reverse, that's it. No CT needed
- Torque control!
That these allows space usage to be reduced!

Also output debug/feedback signals as well such as:
- Speed
- Force
- Error, What is this?!

Another yet, why DC motor has to be connected over interface? Most DC motor I saw in real life are two leads, plus and minus only!
Are you reffering to a BLDC motor?! An advanced motor for drones, skateboard, etc. that has digital brush, and feedbacking like this Principia DC motor.
sdac, your naming is wrong. It should have been named BLDC motor, not DC motor.

Please!!!! Where is the frikin SOURCE CODE!!!???
We want to add this DC motor and interface emmerge into one!!!

Update:
Add CT feedback and its deployment examples. Let the request fully adequate and sufficient enough.