There are a couple of ways to do this. for going forward you can allocate a prop and populate it with both page names when a page name occurs and with the custom link name when exits or custom links occur. Then you can path on that prop. You can set this up in your s_code or in your processing rules. Since you have an event that occurs on the link you want you can always put the page name into the prop but when eventx fires put the custom link name in instead. Now you can path on that prop to find the pages before the event occurs.
Or
you can create a visit segment where 'eventx greater than 0' and then just do your normal path reports. if that event ONLY happens one place you have it. If you need to do it in conjunction with any other data passed when that exit link is clicked you can include that in your segment. Unfortunately sequential segmentation 'then' clause won't let you go back in time (ie visit where eventx is greater than 0 'before'... maybe in the future) so you won't know in some of your reporting if the guy saw page 1, page 2, page 3, clicked the link with the event, came back (because the visit isn't closed yet, saw page 1 again and then page 4 your pathing reports would show 4 but it's not really a path you want.
Or
You can pull a data warehouse report for the custom/exit link name (in a segment) and get all the page names etc and visitor ids and whatever else you need to sequence all the visits yourself (we have a counter evar for visits that increments on every server call, a daily visit number, date and unique visitor id(s) so we can always sort out and get any visitor's data in sequential order.