EV code signing with VSTO add-in

Question

We are a small software company producing VSTO add-ins for PowerPoint, Excel and Word. Recently, more of our clients have been seeing the SmartScreen warning popping up when installing. We would like to avoid this as it tends to lead to a lot of support calls and damages our reputation. We currently sign application manifests and setup.exe files with a GoDaddy code signing certificate. I understand that signing with an EV certificate would probably eliminate the SmartScreen issue. Because EV certificates require hardware key storage and because we build from different locations (DevOps pipelines running on various Azure VMs plus various other machines), the solutions available to allow EV signing seem to be very complex and expensive. I was wondering if we could sign the application manifests with a standard certificate on every build, then when creating new setup.exe files, which we don't do very often, sign the setup.exe with an EV certificate in one location. Is it possible to sign manifests and setup.exe with a different type of certificate? Would that get around the SmartScreen or would the application manifests also need to be signed with an EV certificate?