Your problems don't lay in assembly language, rather the assembler commands specific to that assembler. They are in no way standard at all. You're learning quickly why many around here don't use WLA either. Too much red tape junk. A 'slot'? Really WLA? Most of those WLA commands are junk and have no direct translation with other assemblers.
Instead of sections, banks, slots, or other WLA junk, You'll want to replace that stuff with simple org directives telling the assembler where you want the code to go.
It doesn't seem like you're ready to port anything because you don't yet understand what you need to do with either assembler nor what you need to get a ROM going from scratch.
If you're using xkas, you can simply do something like this:
;add a quick header to the ROM. For HiROM mapping, it is expected to be at $ffc0 in the first bank.
;You should also be able to use use $00ffc0, but I forget if xkas maps that correctly offhand.
db 'ROM TITLE '
db $31 ;lorom ($31 = hirom)
db $02 ;rom+save ram
db $0a ;8mbit rom
db $03 ;64kb sram
db $00 ;japan
db $00 ;no developer
db $01 ;version 1.1
dw $0000 ;inverse checksum
dw $ffff ;checksum
dw $ffff ;brk
dw $8800 ;nmi
dw $8800 ;irq
dw $ffff ;cop
dw $8000 ;reset
;Your nmi and interrupt vectors point here. Right now, it does nothing but return in the event they run.
;Your reset vector points here. This is thus the beginning of code execution.
sei ;disable interrupts
xce ;switch to native mode
jsl $c10000 ;jump to initialization routine.
;Your Initialization Code Could Go Here.
Macros are in the documentation, but I wouldn't complicate matters with those yet.
You should probably work on understanding this tiny framework I've laid out there so you understand what's necessary and what's going on. That should actually compile into a working ROM that you should be able to use the debugger on. However, it doesn't actually do anything visual of course.