You still need an UI to configure the different streams and an interface to start the different streams, as well as a setup in the background that lets you create several encoders at different settings and that can send them to different locations.
The CPU usage from ffmpeg in theory should be very similar to what OBS will use, since both use x264 as their encoder. If you "just" want to send out one stream to several locations the CPU usage would be pretty much the same as when you only send out one stream. But as long as you want different settings for each stream the cpu usage will increase with every stream you add.
So let's say OBS uses 25% of your CPU for one stream. 5-10% of that are probably used to render the Scene. So a second stream will use another 15% of your CPU for example, it could be more/less depending on its settings. This increase will be quite similar to what you see when transcoding with ffmpeg at the moment. Add a third stream with different settings, and the cpu usage will increase further.
Services like twitch(if you are partnered) or youtube do the transcoding for you as most people will not have enough CPU power nor Upload Bandwidth to do it themselves.