yeah, the only problem is that JTR doesn't support AES-128 for AxCrypt files (which is actually the default one for the free version as far as I can tell).
In the forum post I also mentioned that it might or might not be possible to detect if the file uses AES-128 or AES-256 from the file metadata alone (it might be the case that you need to enter a password and the software simply tests both until one succeeds or both fail, this is just an assumption but the AxCrypt spec PDF file hints to it that the cipher is not known).
the cost factor doesn't matter at all (well, only for how slow it is, but not if something is crackable or not)... my perl scripts from the forum post above should clearly show that the algorithms are different and therefore it's currently not cracking.
If we would implement this in hashcat, we probably would add 2 separate hash types "AxCrypt 2 AES-128" and "AxCrypt 2 AES-256" and the user must select one (they should either know the algorithm itself, or at least if they used the paid version etc).
Of course it would be best if the hash format would indicate which AES key size was used, but again, as said above, it might not be possible to detect this with axcrypt2john.py (but maybe there is some way, dunno, also see: https://github.com/magnumripper/JohnTheRipper/blob/a63b64d2ab57606b4c6a8a005452c531c02fe8e6/run/axcrypt2john.py#L20).
Thx (and sorry for not posting here directly yesterday, I was in a hurry and only had time to complete that hashcat forum post)