If there is less than a few GB of data in all the tables and indexes, then mysqld may use only 3GB of RAM. Look on disk in the datadir; see what the total size if that dir tree is. That will be an approximation of how much RAM might be used.
A well tuned mysql will run with under 5% CPU. That includes tuning of the VARIABLES, adding necessary INDEXes, and formulating queries optimally. (Plus other things.)
I once made a 1-line change to a SELECT and it changed from 50% CPU all the time (there were 2 cores) to under 2%.
You say the import is slow? How big is the import file? How long would it take to read that file? The import will be only a small factor slower than the time to read the file.
Check the import file -- does it have INSERT statements that each have lots of rows? That is critical to the speed of import.
Do you have lots of FOREIGN KEYs? Lots of secondary indexes? These may impact the speed.
The import is single-threaded. Multi-threading it (which is not easily done) is mostly useless, since you are probably nearly I/O-bound.
If it has been running for a long time without filling up much disk, then connect and do
SHOW PROCESSLIST; to see what it is doing. That might be a useful clue.