There is no uncompressed P2(W)SH address
As far as I know, it's non-standard, but there can be such valid transaction. I don't know if it was standard in versions prior the currents.
but since this tool was built before Segwit became a thing, I would rule out different private key types as being the cause (as long as this person was aware of this fact).
Before Segwit, wasn't there only P2PKH and P2SH as single-sig address types? So it's normal that it printed him two types.