Will it help instead of planning to shrink database log file regularly?
Absolutely not! Shrinking a file - data or log - is an exceptional event. It is something you do after has been an accident that cause a file to grow, or, in case of a data file, you have purged a lot data. Shrinking a log file could also be relevant if you have taken an action that you know will reduced the amount of log records being produced.
Shrinking a log file regularly is not only meaningless, but it is a bad thing to do. It's bad, because when the log file has to grow, the disk has to be zeroed out and that takes resources, and stalls the process that triggers the autogrow.
Delete large number of rows and tables without growing the transaction log?
That's very easy to achieve: don't shrink the log, but keep it at a size where it can fit the workload.
By the way, creating and dropping tables does not produce a lot of transaction log, as that is just metadata. Writing lots of rows to these tables will of course produce a lot of transaction log. However, dropping these big tables will not, since all that needs to be logged is metadata and the extent deallocations. (But if they delete data with the DELETE statement, that again produces plenty of log records.)