If my SQL Server is too busy should I make a SQL Server transaction log backups? (4369040)

Yes, you should always make regular SQL Server transaction log backups if you want to ensure safe preservation of all your data.

One of the biggest performance intensive operations in SQL Server is an auto-grow event of the online transaction log file. By not making transaction log backups often enough, the online transaction log will become full and will have to grow. The default growth size is 10%. The busier the database is, the quicker the online transaction log will grow if transaction log backups are not created.

Creating a SQL Server transaction log backup doesn’t block the online transaction log, but an auto-growth event does. It can block all activity in the online transaction log.
This is why it is crucial we have full database backup chain.
One more reason its not enough to have only full database backup to recover everything that is lost is the fact that full backup is not doing backup of all transactions from the online transaction logs.
Regularly created transaction log backups are mandatory here to ensure no data is lost.