I managed to have one ap (A) and the second mikrotik (B) configured as wds slave, but then, when A is off, B doesn't provide an access point.
MT doesn't have anything like "fallback" for repeater AP. What often repeater AP does is that it uses radio (master wifi interface) to connect to serving AP as wireless station and provides AP functionality via same radio (slave wifi interface). Basic requirement for radio station is possibility to change physical radio parameters (e.g. frequency, channel layout, ...) to be able to follow changes of AP. When master radio is not connected, it's actively searching for AP to connect to, during which it's constantly changing frequency). So not really suitable for AP operations.
Next obstacle is the fact that "true" repeater actually acts in the same way as (dumb) ethernet switch: it only passes ethernet frames between member ports. So it doesn't provide DHCP server (and the rest of network functions). If link from slave AP to master AP drops, then also these functionalities get lost.
Alternative is to configure slave AP as WISP CPE (not sure if such a profile exists in QuickSet, probably not). In this case device does routing (and NAT and what not) between WAN interface (which is wireless in this case) and LAN interfaces (wired ports, and slave wifi interface). In this case network functions remain working if "WAN" link gets lost, the problem with scanning wifi interface still remains.
The problems, outlined above, are the reason for using dedicated wifi radio for uplink/meshing. E.g. Audience, device made by MT with published intent of providing wireless mesh capabilities, comes with 3 radios: 2.4GHz radio and two 5GHz radios - one of them is intended for meshing between nodes and one for AP on 5GHz band.