Joining the tables in the database should perform better than joining them on the application layer. If it doesn't, there's something very odd.
This holds for any production ready DBMS. Even the ones that don't care about performance or preserving your data.
But wrong is almost always odd, so the normal expectation is that you understand the oddity on your system. Otherwise you are blind to problems.
Anyway, it's also not common for an application to have "reduce total CPU usage" as a goal. Available CPU on the database is way more valuable than on the application server, and so it makes sense to trade them up.
Check in on your databases periodically, and refresh your memory. There's a very real chance they've picked up features that'll make your life a lot easier.