If you want to control the amount of data that zsh stores in its history files the look at the zsh user guide section 2.5.4 and set HISTSIZE and SAVEHIST
As for the .asl logs they are written to be any application, they are the database of Apple's logging mechanism. zsh will not read or even know of these files unless you run command to look at them. Thus I do not see how their size would affect zsh's startup time.
However doing some googling (it helps to show in the question what you have found) It appears that there might be an issue with the login command (which is not zsh but used by the mechanism to start shells). See this thread for some comments - starting from your idea of deleting all .asl files to what seems a more reasonable explanation. login without the -q flag seems to do an ASL query for last login and that causes a slowdown. The suggestion given there and elsewhere is
The correct way to bypass the ASL query is to set Terminal to open shells with /bin/bash (or your shell of choice) instead of the default login shell. Terminal will still use /usr/bin/login to launch the shell, but it passes the -q switch to prevent the ASL query.
Note that deleting the .asl files removes all information logged by applications and so doing this removes all chance of seeing what happened on your machine. I think that losing this data is not worth saving a few seconds on startup of terminal, just leave terminal open or try the fix suggested.