Looking at IPKN in LittleNavMap, the localizer appears to be in the correct location in both the default sim nav data, and when using Navigraph. (The beam width is narrower in default). The localizer is located on a mountain peak at a ski resort south of the airport.
With both default and Navigraph, the localizer points “the wrong way” on the map (to the southeast), because an aircraft using this for the missed approach would actually fly the back course portion of the localizer which points to the northwest. On the approach chart, it indicates that even though it is a back course, it has “normal sensing” meaning that the left and right sides of the beam are swapped.
Normally when flying a localizer back course, the needle response is opposite - if the needle drifts right of center, you would fly away from the needle (to the left) to bring it back to center.
It is likely that the nav receiver in MSFS aircraft does not have the ability to handle a back course ILS beam with normal sensing.
One way of dealing with this would be to set the course on the CDI to the reciprocal of the localizer front course - i.e. 123 degrees instead of the published 303 degrees. This would only work with an HSI course indicator - it would not work with a simple GA-style OBS/CDI gauge where the CDI needle is hinged at the top and does not rotate with the course selector.
Unfortunately, even with a rotating HSI, all default Asobo aircraft lock the course on the CDI to whatever localizer course is contained in the nav data as soon as a localizer is within reception range. The HSI ILS course setting cannot be changed once an ILS is being received.
There is probably nothing that can be done in the nav data itself when using default MSFS aircraft to make this back course/normal sensing localizer work the way it is supposed to. When trying to fly it outbound, you would have to fly away from the needle to bring it back to center as if it was a “standard” back course.