This is a great question, and the answer is, perhaps surprisingly, that we care about PPT simulators in perfectly secure MPC also because of computational hardness.
Concretely, if you design a perfectly secure MPC protocol, you can prove it secure with an inefficient simulator. This will be a valid proof of security for the perfectly secure protocol, but there is an important catch: perfectly secure MPC protocols exist in the model where the parties have access to ideal (private, authenticated) communication channels. The trouble is, in the real-world, you will usually instantiate these channels using public key cryptography, hence making a computational assumption. However, the security proof of your perfect MPC protocol with idealized channels does not imply the security of this real-world version (where the channels are instantiated via a public key infrastructure) if the simulator is inefficient! So if you have a perfect MPC protocol and want to use it in the real-world, you have to find a "non-computational" way to instantiate the secure authenticated channels, and that's quite inconvenient.
Mostly for this reason, it is therefore generally advocated to prove security of perfectly secure protocols with a PPT simulator. That way, you're guaranteed to remain secure if some of the "idealized components" of your protocol are later replaced with computational instantiations (typically the channels, but it can also be other idealized functionalities).
For a bit more discussion on this point, you can read the discussion starting at the end of page 85 of this paper by Asharov and Lindell, which is generally a great resource to better understand the security analysis of MPC protocols.