You're comparing two different kinds of defenses that work against two different kinds of threats, without stating what kinds of secrets you're trying to protect or what kinds of threats you're trying to defend against. And you're not giving us full protocols to work with, so we're going to make guesses about what you're trying to do. So please understand in advance if the answer doesn't meet your expectations.
The first thing to remember about salt is that it's not kept secret, and it's not intended to be kept secret. The sole reason salt exists is to make it difficult to guess the value of the data in the case where the data being hashed needs to remain secret AND it's possible that the data may collide with other data. For example if you and I both chose the same password and both password hashes are kept in the database, someone looking at the database could see that the hash of my password is the same as yours. But when I know your salt (remember, salt is not secret), I can try to brute-force guess your secret by running my guesses through your salt+hash algorithm.
The next question is how are you encrypting the hash? Are all hashes encrypted with the same key? If so, then collisions between secrets are still possible and it behaves no differently than an unsalted hash. For example, if my secret is "Squeamish Ossifrage", the hash digest might be 123456, and the encrypted hash digest using key ABC might be XYZ999. If your secret is also "Squeamish Ossifrage", then your hash digest is also 123456, and the encrypted hash digest using key ABC is also XYZ999. An attacker could compare entries in the database and by seeing we both have XYZ999 would know that your secret is the same as mine.
Encrypting a hash with a secret key does one thing: it prevents someone else from computing the hash because they don't know the secret key. Otherwise, it functions equivalent to a hash.
And do NOT worry about "a decryption algorithm could be cracked." If you've chosen a strong algorithm as you stated in your preconditions that's not a realistic concern. (And if you've chosen AES-256 and it's cracked, the whole world has a lot more to lose than whatever secrets you're keeping.)