Going against the grain - backing up and truncating the tran log
I'm assuming you have these databases in FULL RECOVERY because you need to be able restore to a point in time.  If that's NOT the case, then use SIMPLE mode and your log would only grow to the size needed to contain a transactional unit of work (which could be index maintenance as well as application transaction).

Now, back to the FULL RECOVERY model.  Backing up the log on a periodic cycle (whether it's 1 minute or 15 minutes) is only going to help you if transactions are able to commit during that time frame.  Active long running transactions will prevent that log space from being flagged for reuse.

There shouldn't be a problem with running transaction log backups every minute (Back Up Transaction Logs Every Minute. Yes, Really).

Constantly shrinking the log will have a negative performance impact due to waiting for the log to grow again.  Logs do not honor Instant File Initialization.

The bottom line is:

The transaction log has to be large enough to hold an active unit of work and you need timely log backups to allow of log reuse.