Bowtie1 does not report any indels. If an indel is in the middle of a read, the read will be unmapped. If the indel is close to the end of a read, it will be mapped with multiple mismatches towards the end. Bowtie2 and the bwa series are able to map reads with indels.
Most variant callers can only call indels when the mapper reports them. GATK HaplotypeCaller (HC) is an exception. It does local assembly and is able to call an indel even if no reads are mapped with the indel. HC indel calling might work with bowtie1 alignment at least in theory, but even if it works, the sensitivity is probably low. Anyway, for variant calling, don't use bowtie1. Use bowtie2/bwa/bwa-mem or other modern mappers.
BTW, whether to allow indels in seeds is not critical. Both blasr and bwa-mem use exact seeds and they work well with PacBio reads with ~15% indel error rate (or >20% for read-to-read mapping). As to chimeric alignments, most Sanger read mappers report them. In the local multi-hit mode, bowtie2 and a few other NGS mappers can find chimeric alignments as well. Bwa-sw has been reporting chimeric alignments by default since 2010. Bwa-mem does that, too.
How long are the INDELs you're looking for?