Hi @Erin_Heminover , I tested the same - you are right, your rule will not run because the task type is just a normal task. The rule action is was inferring would be listed under the Convert to actions, which unfortunately does not exist.
If that were the case, that would solve your problem that when a task is added via email, convert to a task type.
However, that would consume a Rule action (which is not ideal for Starter or Advanced tiers which have, currently soft limitations).
Another idea would be to set the task type whenever a task is added to the project, be it via email or multihomed from another project. However that may have undesired effects for some users, so that would need to be an, i.e. a feature that could be toggled per project.
I have gone ahead and created a product feedback request for the former, here.