Our approach would be to have 釣り上げる as a search-only key, and drop the restrictions.

@@ -15,2 +15,2 @@
-<keb>釣り上げ</keb>
-<ke_inf>&iK;</ke_inf>
+<keb>釣り上げる</keb>
+<ke_inf>&sK;</ke_inf>
@@ -22,2 +21,0 @@
-<stagk>吊り上げる</stagk>
-<stagk>吊上げる</stagk>

値段の釣り上げ	65	6.4%   <--- sense 2
値段の吊り上げ	469	46.1%
値段のつり上げ	484	47.5%
値段の吊上げ	0	0.0%

価格釣り上げ	316	8.6%  <--- sense 2
価格吊り上げ	2077	56.7%
価格つり上げ	1211	33.1%
価格吊上げ	60	1.6%


LOTS of hits:
https://x.com/search?q=値段の釣り上げ&src=typed_query
in either form:
https://x.com/search?q=値段の吊り上げ&src=typed_query

Example:
https://x.com/Gr00vin_Magic/status/1769282323902542161
駿河屋さんへ。値段の釣り上げやめてください。なぜ3万円も値上げしたんですか？

If you search for "釣り上げる" or "釣り上げ" today in jmdict you won't find this entry, and I think you should.

Just encountered in professional subtitling in 3-way negotiation for an item.
まぁ、そんなわけで値段の釣り上げ交渉ってわけだ

This looks to be either intentional, or a super-common misspelling. MacOS and Android both give 釣り上げ as the first IME result, and metaphorically it's not surprising that Japanese natives might think this makes sense. (A Japanese eggcorn?)

I agree with the split from 9 years ago, sankoku has the same split. Not sure if/when a proper kokugo would ever bless this usage, but I think this is prevalent enough that it needs to be searchable. I'd usually [sK] a mere "spelling mistake", but this seems have gained a significant degree of acceptance in daily use.

@@ -13,0 +14,4 @@
+<k_ele>
+<keb>釣り上げ</keb>
+<ke_inf>&iK;</ke_inf>
+</k_ele>
@@ -17,0 +22,2 @@
+<stagk>吊り上げる</stagk>
+<stagk>吊上げる</stagk>

吊り上げる 28,599  65.8% 
つり上げる 11,431  26.3% 
吊上げる　    776   1.8% -sK
つりあげる  2,684   6.2%

@@ -12 +12 @@
-<ke_inf>&io;</ke_inf>
+<ke_inf>&sK;</ke_inf>