What IP are you providing in the redirect to get to the portal? If it's an RFC1918 private address (10.x.x.x, 172.16.x.x, or 192.168.x.x) then you don't have an alternative, as those IPs are no longer allowed in certs issued by Trusted Anchors. I would suggest that your best option would be to setup a DNS server for your guests that doesn't communicate with your internal servers, then you could get a trusted cert with the dns of your ISE server portal(s) using something like ISE1.<domain> ISE2.<domain> and have it resolve internally on your guest DNS on a private IP.
With changes coming on mobile devices, they will soon not be able to bypass that warning and using private IPs for the redirect will no longer function.
The only other solution would be to use a publicly resolvable IP for the portals, so it's down to use a public IP for each portal, have a guest DNS, or risk having devices that will increasingly stop working on your guest network altogether. HTH.